development-kitlisted

Route an idea, feature, or existing repository through the canonical product, specification, UX, visual design, implementation, verification, and release owners without creating competing documents. Use when the user asks for the development kit, a complete development workflow, which skills or Markdown artifacts to use, or how planning should hand off to UI/UX and full-stack delivery. Also routes safe extraction from an explicitly supplied worked example. Not a substitute for specialist methodology, implementation, or approval.
ongkipro/dotfiles · ★ 0 · Data & Documents · score 53

Install: claude install-skill ongkipro/dotfiles

# Development Kit Control Plane Own the route and gates, not every deliverable. Select the smallest complete path, name the canonical artifact and specialist for each changed fact, and keep one requirements source, one execution queue, and one implementation truth. Read [Reference map](references/reference-map.md) only when the requested path or artifact owner is unclear. Read [Market engineering](references/market-engineering.md) only for activated Indonesia/Malaysia market concerns. For cross-CLI skill upgrades or comparisons with Claude, OpenAI, Kimi, or shadcn, read [External ecosystem adoption](references/ecosystem-adoption.md). When changing the shared skill system itself, also read [Skill evaluation contract](references/skill-evaluation.md). Do not assume a local worked-example directory exists. ## 1. Resolve authority before work 1. Inspect repository instructions, existing product/spec/design/runtime documents, `TASKS.md`, code, tests, and status evidence. Disk wins. 2. If no repository exists, stage accepted planning under `~/Documents/work/prd/<slug>/`; promote it only through `project-init` after explicit development authorization. 3. Extend an existing canonical artifact. Never create a second PRD, task queue, architecture, UX contract, design-system spec, or readiness report. 4. Label unresolved facts `Unknown`, `Assumption`, or `Proposal`; Markdown is intent, not runtime proof. ## 2. Choose one planning lane - Unresolved market, pricing, au