willyu1007

Documentation conventions overview. Keywords: documentation, conventions, overview.

High-level repository architecture overview. Keywords: architecture, overview, structure.

Documentation conventions overview. Keywords: documentation, conventions, overview.

High-level repository architecture overview. Keywords: architecture, overview, structure.

How to author execution-ready plans. Keywords: plan, authoring, execution.

Guidelines for creating execution plans. Keywords: plan, guidelines, execution.

Modular system architecture and module instances. Keywords: modules, modular, architecture.

Backend service patterns for Node.js/Express/TypeScript (layering, validation, config, monitoring, testing). Keywords: backend, api, express, node, typescript, service patterns.

Use only in repos that still include the `init/` bootstrap kit to produce Stage A/B/C artifacts, update skill pack selection, and sync provider skill wrappers.

Create a goal-aligned macro-level roadmap artifact (dev-docs/active/<task>/roadmap.md) by asking clarifying questions and recording assumptions; planning only (no code changes).

Build a complete, production-embedded Agent module for a real feature request (API + optional worker/sdk/cron/pipeline), including blueprint, scaffolded runtime, prompt pack, docs, and registry entry. Enforces explicit user approvals, no-secrets-in-repo, fixed API route names (run/health), and conversation/memory strategy decisions.

Entry workflow for LLM engineering tasks (provider integration, calling wrapper, routing profiles, prompt templates, cost/telemetry, credentials/config keys). Routes to one procedure and enforces required verification.

Read-only progress reporter. Produces a structured status snapshot from existing project/task artifacts (project hub + dev-docs) and includes an actionable next command; never modifies repo files.

Define and execute a distinctive visual direction for net-new UI or brand refresh work (art direction, typography, color, motion, composition), then deliver a polished reference implementation. Primary intent: creative design direction and visual differentiation; pairs well with style-frontend-ui and build-react-components for engineering hardening.

GitHub Actions CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.

GitLab CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.

Treat convex/schema.ts as the database Single Source of Truth, initialize Convex scaffolding, regenerate docs/context/db/schema.json and docs/context/convex/functions.json, and verify the repository stays aligned with Convex mode.

Mirror schema changes from a real database (SSOT) into repo artifacts (prisma/schema.prisma + db/schema/tables.json) and refresh LLM context (docs/context/db/schema.json).

Apply schema changes from repo SSOT (prisma/schema.prisma) to a target DB via Prisma migrations, with diff preview + approval gate; then refresh LLM context (docs/context/db/schema.json).

Enable and operate the Deployment feature (ops/deploy conventions + deploy scripts) for multi-environment delivery.

Plan/apply/verify cloud environment config and secret references using env contract + policy/inventory routing; detect drift, rotate secrets, and decommission environments with approval gates. Use for staging/prod deployments and maintenance.

Maintain env contract SSOT (env/contract.yaml), validate env/values + env/secrets refs coverage, and generate env/.env.example + docs/context/env/*. Use when adding/renaming/deprecating config keys.

Bootstrap, diagnose (doctor), and reconcile local dev environment from env contract/values/secret refs; generate .env.local and redacted docs/context/env/effective-*. Use when local env is broken or needs syncing.

Enable and operate the Packaging feature (ops/packaging conventions + ctl-packaging) for building runnable artifacts (usually container images).

Evidence-driven debugging loop with mandatory instrumentation + fix approvals, run_id-tagged logs, default 3-pass verification for flaky issues, and guaranteed cleanup of debug-only instrumentation.

Design or review a layered backend architecture (routes, controllers, services, repositories) for HTTP APIs and microservices.

Apply cross-cutting backend service patterns across routing, services, repositories, validation, configuration, errors, and tests.

Manage backend configuration safely with typed, validated settings and clear separation between defaults and secrets.

Apply safe and maintainable backend database patterns (transactions, pagination, soft deletes, query optimization, data consistency).

Build backend service and repository layers to isolate business logic from persistence and improve testability.

Handle async/await and error propagation in backend services with consistent error types, wrappers, and response mapping.

Implement or refactor backend HTTP routing and controllers using a layered pattern (routes delegate, controllers validate and call services).

Project-level orchestrator for intake and continuity. Turns a new/ongoing request into a governance decision (reuse vs new task, mapping to Milestone/Feature/Requirement), keeps the project hub consistent (registry/changelog/derived views), and ensures LLM-authored semantic extraction is captured in structured non-AUTO sections. Focuses on planning and coordination, not product code changes.

Read-only progress reporter. Produces a structured status snapshot from existing project/task artifacts (project hub + dev-docs), can include semantic focus extracted from LLM-authored feature briefs, and includes an actionable next command; never modifies repo files.

Project hub synchronizer and validator. Scans the repo (including multiple dev-docs roots), validates project/task metadata against the Project Contract, repairs drift by generating missing task identity meta (.ai-task.yaml) and regenerating derived views, and enforces complete task-feature mapping plus LLM-authored semantic extraction for feature-level governance.

Enable and operate the Context Awareness feature (docs/context contracts + environment registry) so LLMs can work from a verified context layer instead of ad-hoc repo scans.

Enable and operate the Packaging feature (ops/packaging conventions + ctl-pack) for building runnable artifacts (usually container images).

Enable or disable skill packs via ctl-skillpacks and re-sync provider wrappers without manually editing the manifest.

Enable and operate the CI feature (GitHub Actions / GitLab CI) with repeatable templates, artifact conventions, and opt-in delivery enablement.

Define and execute a distinctive visual direction for net-new UI or brand refresh work (art direction, typography, color, motion, composition), then deliver a polished reference implementation. Primary intent: creative design direction and visual differentiation; pairs well with style-frontend-ui and build-react-components for engineering hardening.

Apply local React patterns (derived state, memoization, callback stability, controlled inputs) to improve predictability and render efficiency inside components. Primary intent: component-internal logic quality and render behavior; complements but does not replace routing/data/styling skills.

Orchestrate end-to-end frontend feature implementation across components, hooks, routing, data fetching, styling, and user-visible states with consistent architecture and verification. Primary intent: cross-cutting implementation alignment; pairs with specialized skills when one concern needs deeper treatment.

Build or refactor React components with typed props, clear composition, and explicit interaction/loading/empty/error behavior. Primary intent: component contract and behavior correctness; pairs with styling or design-direction skills for visual decisions.

Define and execute a distinctive visual direction for net-new UI or brand refresh work (art direction, typography, color, motion, composition), then deliver a polished reference implementation. Primary intent: creative design direction and visual differentiation; pairs well with style-frontend-ui and build-react-components for engineering hardening.

Implement and normalize UI styling within an existing design system using theme tokens, reusable style primitives, responsive rules, and accessibility checks. Primary intent: styling execution consistency; can follow frontend-design when a creative direction needs maintainable implementation.

Implement resilient loading/empty/error/permission/retry UX states for async interfaces with user-safe messaging and recoverable flows. Primary intent: failure-state UX quality; pairs with component, data-fetching, and UI-guideline skills when needed.

GitHub Actions CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.

GitLab CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.

Entry workflow for LLM engineering tasks (provider integration, calling wrapper, routing profiles, prompt templates, cost/telemetry, credentials/config keys). Routes to one procedure and enforces required verification.

Enable and operate the CI feature (GitHub Actions / GitLab CI) with repeatable templates, artifact conventions, and opt-in delivery enablement.

Plan/apply/verify cloud environment config and secret references using env contract + policy/inventory routing; detect drift, rotate secrets, and decommission environments with approval gates. Use for staging/prod deployments and maintenance.

Bootstrap, diagnose (doctor), and reconcile local dev environment from env contract/values/secret refs; generate .env.local and redacted docs/context/env/effective-*. Use when local env is broken or needs syncing.

One-command UI governance gate that enforces the data-ui contract + semantic-token Tailwind policy and (optionally) orchestrates ESLint/Stylelint/Playwright under the same evidence run directory.

Bootstrap, diagnose (doctor), and reconcile local dev environment from env contract/values/secret refs; generate .env.local and redacted docs/context/env/effective-*. Use when local env is broken or needs syncing.

Enable and operate the Context Awareness feature (docs/context contracts + environment registry) so LLMs can work from a verified context layer instead of ad-hoc repo scans.