@vpxa/aikit 0.1.97 → 0.1.99

package/scaffold/dist/definitions/skills.mjs

@@ -2300,6 +2300,46 @@ Wait for the user's response. If they request changes, make them and re-run the
 - **Incremental validation** — Present design, get approval before moving on
 - **Be flexible** — Go back and clarify when something doesn't make sense
 
+## Challenge Discipline
+
+Every design MUST be stress-tested before presentation. Apply these checks:
+
+### 1. Domain Model Cross-Reference
+
+Before presenting any design, \`search\` curated knowledge for existing glossary, domain models, and naming conventions. The design must use **canonical terms** from the codebase — not synonyms, not approximations.
+
+- If the design introduces a new term, justify why no existing term works
+- If fuzzy language exists ("handle the thing", "process the data"), sharpen it to precise domain terms
+- Cross-reference proposed interfaces against existing code: do the names, shapes, and flows match what's already there?
+
+### 2. Contradiction Detection
+
+Search the codebase for existing implementations that touch the same domain:
+
+- Does the proposed data flow contradict existing patterns?
+- Do proposed error handling strategies conflict with established conventions?
+- Are there implicit assumptions that contradict documented decisions?
+
+If contradictions exist, surface them explicitly: "This design proposes X, but the existing code does Y in [file]. Which should win?"
+
+### 3. Specification Precision
+
+Before finalizing each design section, apply this test:
+
+> "Could two competent developers independently implement this section and produce compatible results?"
+
+If no — the spec is too vague. Add:
+- Concrete examples (input → output)
+- Boundary conditions (what happens at 0, 1, MAX?)
+- Error cases (what fails, what's the recovery?)
+
+### 4. Living Documentation
+
+During the brainstorming session, when design decisions clarify existing ambiguity:
+- Note which existing docs/comments are now outdated
+- Include documentation updates as part of the design output (not a separate "docs task")
+- The design doc itself becomes the canonical reference — don't create knowledge that lives only in chat
+
 ## Visual Presentation Support (Advanced Mode Only)
 
 Use the \`present\` MCP tool for showing mockups, diagrams, and visual options during brainstorming. It is available as a tool, not a separate mode. Choosing this means you can present rich visual output when it helps; it does NOT mean every question should become visual.

package/packages/cli/dist/constants-BSGpNyrr.js

@@ -1 +0,0 @@
-const e=`aikit`,t={type:`stdio`,command:`node`,args:[`-e`,[`const{execFileSync:x}=require('child_process')`,`const{renameSync:m}=require('fs')`,`const{join:j}=require('path')`,`const d=process.platform==='win32'?j(process.env.LOCALAPPDATA||'','npm-cache','_npx'):j(require('os').homedir(),'.npm','_npx')`,`const s={stdio:'inherit',shell:true}`,`try{x('npx',['-y','@vpxa/aikit','serve'],s)}`,`catch(e){try{m(d,d+'_'+Date.now())}catch{}`,`x('npx',['-y','@vpxa/aikit','serve'],s)}`].join(`;`)]},n=[`aikit`,`brainstorming`,`multi-agents-development`,`session-handoff`,`requirements-clarity`,`lesson-learned`,`c4-architecture`,`adr-skill`,`present`,`frontend-design`,`react`,`typescript`,`docs`,`repo-access`],r=[`aikit-basic`,`aikit-advanced`,`_epilogue`],i={"chat.agentFilesLocations":{"~/.claude/agents":!1},"github.copilot.chat.copilotMemory.enabled":!0,"chat.customAgentInSubagent.enabled":!0,"chat.useNestedAgentsMdFiles":!0,"chat.useAgentSkills":!0,"github.copilot.chat.switchAgent.enabled":!0,"workbench.browser.enableChatTools":!0,"chat.mcp.apps.enabled":!0,"chat.instructionsFilesLocations":{"~/.copilot/instructions":!0,".github/instructions":!0}};export{i as a,n as i,t as n,e as r,r as t};