Followup audit of the single-source-of-truth agent-docs rollout. Several AI.dev prompts and skills still taught agents the old 8-file pattern (which would re-introduce drift) and the generator script emitted a misleading summary in --no-commit mode. AI.dev guides: - Delete AI.dev/SKILLS/update-agent-docs.md — entire doc taught the old 8-file pattern. Canonical reference is now .windsurf/workflows/repo_update-agent-docs.md. - AI.dev/SKILLS/index.md + README.md: replace dangling 'Update Agent Documentation' link with pointers to agent-behavior-guidelines.md, agent-onboarding.md, and the workflow doc. - AI.dev/SKILLS/scan-repo-context.md: remove instructions to read .windsurfrules / write .cursorrules. Point at the canonical behavior file. - AI.dev/PROMPTS/new-product-scaffold.md: remove .windsurfrules and CLAUDE.md from the scaffold tree. Add deprecated-files callout + regeneration hint. - AI.dev/PROMPTS/agents-md-sync.md: drop 'Step 4 update CLAUDE.md', point at the generator instead. Remove CLAUDE.md from `git add`. - AI.dev/PROMPTS/ecosystem-audit.md: replace 'CLAUDE.md exists?' with 'canonical-behavior-pointer block present? legacy files absent?'. Script UX: - scripts/update-agent-docs.sh: stop printing 'All repos already in sync' when --no-commit suppressed commits or --dry-run was used. Emit accurate per-mode summaries instead. |
||
|---|---|---|
| .. | ||
| agents-md-sync.md | ||
| backend-module-crud.md | ||
| cross-repo-debug.md | ||
| dependency-health-check.md | ||
| docker-production-prep.md | ||
| ecosystem-audit.md | ||
| new-product-scaffold.md | ||
| platform-integration.md | ||
| prd-to-implementation.md | ||
| pre-release-validation.md | ||
| README.md | ||
| refactor-with-tests.md | ||
| roadmap_execution.md | ||
| roadmap-execution.md | ||
| test-gap-analysis.md | ||
| type-safety-sweep.md | ||
ByteLyst Ecosystem — Reusable AI Prompts
Location:
AI.dev/PROMPTS/Audience: Claude Code, Codex, Cursor, Copilot, Windsurf Cascade, Gemini, and any AI coding agent. Scope: All 37 repos inD:\BYTELYST\CODE\— common platform, product repos, tooling repos.
How to Use
Copy-paste a prompt into your AI assistant, or reference it by path:
@file AI.dev/PROMPTS/roadmap-execution.md
Each prompt is self-contained — it includes the context the agent needs without requiring you to manually explain the ecosystem every time.
Prompt Index
🗺️ Planning & Roadmap
| Prompt | Purpose |
|---|---|
| roadmap-execution.md | Execute a phased roadmap with checkpoints, commits, and validation |
| new-product-scaffold.md | Scaffold a new ByteLyst product repo from scratch |
| prd-to-implementation.md | Convert a PRD into a concrete, phased implementation plan |
🔧 Development & Debugging
| Prompt | Purpose |
|---|---|
| cross-repo-debug.md | Systematically debug issues spanning multiple repos |
| backend-module-crud.md | Add a complete Fastify CRUD module (types → repo → routes → tests) |
| platform-integration.md | Wire a product repo into the common platform ecosystem |
| refactor-with-tests.md | Safely refactor code with test-first methodology |
🧪 Quality & Testing
| Prompt | Purpose |
|---|---|
| test-gap-analysis.md | Identify and fill test coverage gaps in any repo |
| type-safety-sweep.md | Fix TypeScript errors across a repo or the workspace |
| dependency-health-check.md | Audit and update dependencies across repos |
📦 Release & Ops
| Prompt | Purpose |
|---|---|
| pre-release-validation.md | Full pre-release checklist: build, test, lint, security |
| docker-production-prep.md | Prepare Docker images for production deployment |
📚 Documentation
| Prompt | Purpose |
|---|---|
| agents-md-sync.md | Update AGENTS.md across all repos to match current state |
| ecosystem-audit.md | Full ecosystem health audit with actionable report |
Conventions
- Agent-agnostic: Prompts work across Claude, Copilot, Cursor, Windsurf, Gemini.
- Ecosystem-aware: Each prompt embeds the key ByteLyst conventions (productId, Fastify module pattern, @bytelyst/* packages, pnpm workspace).
- Commit-friendly: Prompts that produce code changes include commit message guidance.
- Incremental: Each prompt favors small, validated, committed steps over big-bang changes.
Adding a New Prompt
- Create
AI.dev/PROMPTS/<prompt-name>.md - Include a YAML-style header with
name,description,argument-hint - Add it to this index
- Commit:
docs(prompts): add <prompt-name> reusable prompt