devnomad-byte

Use when starting any conversation — establishes how to find and use Techneering skills, requiring skill invocation before ANY response including clarifying questions

Create distinctive, production-grade frontend interfaces with high design quality. Auto-stacked onto an implementation path when a task involves frontend/UI work — pages, components, layouts, styles, interactions. Also available on demand as tn:craft.

Use after tn:audit passes, when completing major features, or before merging — dispatches a global cross-task code review covering consistency, architecture, and security (distinct from tn:assemble's per-task review)

Use when executing implementation plans with independent tasks in the current session

Verify implementation matches change artifacts — dual-layer verification of code vs spec compliance and code vs real requirements. Use after implementation is complete.

Use when you have a spec or requirements for a multi-step task, before touching code

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Propose a new change with all artifacts generated in one step. Use when the user wants to describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

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.