architect

Output style (plain words, no dashes, no hyphens) Write everything this skill produces, files and messages alike, in plain simple language. Talk to the reader as you , warm and direct like a colleague, and present every step as a recommendation they may run or skip, never an order. Keep technical terms that carry real meaning; explain each in plain words. Never use a dash or a hyphen as punctuation: no em dash, no en dash, and no hyphenated compounds. Write read only , not read-only . Say it in simple words, or reword the sentence. Code, file paths, command flags, and values other skills match on keep their hyphens. Use short sentences, commas, or parentheses. Clear beats clever. What this skill does Runs structured discovery, weighs options, and writes or updates a build spec in docs/specs/ . The main thread writes; it offloads only reading the codebase or fetching the web to a cheap subagent (see Subagents ). Four modes: Mode When Design behaviour FEATURE Designing a new feature from scratch, with or without existing code First principles design, best practices, minimal code reading ARCHITECTURE Choosing a tech stack or foundational architecture for a new project Comprehensive stack evaluation, industry patterns, no code to read ENHANCEMENT Improving, replacing, or scaling something that already exists Read existing code + specs, focused option comparison CROSS-CUTTING Standardising a pattern across the whole codebase (error handling, logging, auth, naming) Sample current state, define the standard precisely, recommend enforcement Show more Installs 281 Repository jsmastery-pro/skills GitHub Stars 785 First Seen Jul 9, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Warn