cosmosmith

Generate or update project instruction files for Cosmosmith-governed projects. Use when the user wants AGENTS.md, CLAUDE.md, Cursor rules, Copilot instructions, OpenCode, Trae, or other editor/agent rules created from Cosmosmith conventions, or when they ask how agents should load and follow project rules.

Design architecture, boundaries, data flow, reliability, security, and integration strategy for a Cosmosmith proposal. Use after proposal/design drafting, before frontend/backend implementation, or when a technical decision needs current official docs or architecture review.

Implement backend task slices from a Cosmosmith task ledger. Use when task.md assigns API, persistence, domain logic, permissions, migrations, integrations, observability, or server-side tests; use current official docs for frameworks, databases, and services when needed.

Prepare build, CI, environment, deployment, monitoring, rollback, and release readiness for a Cosmosmith project. Use when tasks approach release, when setup/deploy commands are missing, or when current platform docs are needed.

Implement frontend task slices from a Cosmosmith task ledger. Use when task.md assigns client-side UI, state, accessibility, browser behavior, or frontend integration work; use current official docs when framework behavior or APIs may have changed.

Research current competitors, analogue products, user expectations, pricing, regulations, and ecosystem patterns for a Cosmosmith idea. Use after product discovery or whenever product, design, architecture, QA, or DevOps decisions depend on current external facts.

Verify Cosmosmith tasks against acceptance criteria and produce QA evidence. Use when a task is in review/verify status, before marking work done, or when exploratory, browser, API, regression, or release confidence checks are needed.

Design user flows, screen structure, interaction states, accessibility, and visual direction for a Cosmosmith proposal. Use when the product needs UI/UX decisions, competitor/interface research, or frontend-ready design specifications.

Review Cosmosmith artifacts, task ledgers, generated project rules, and skill outputs for coherence, layer separation, missing evidence, and rule drift. Use before marking Cosmosmith planning or implementation tasks done, after spec generation, or when project rules and generated rules may have diverged.

Turn a rough product idea, vague user desire, or early "create a world" concept into a concise Cosmosmith idea brief. Use when the user has not yet provided a clear problem, target user, first valuable slice, or acceptance criteria; may use web research when market context is current or competitive.

Convert Cosmosmith idea and research briefs into proposal, design, and task ledger artifacts. Use after product discovery, when a rough idea needs an OpenSpec-like proposal, buildable design, and claimable tasks with acceptance checks and verification evidence.