VF Agent Knowledge System

The old “AI Co-Pilot” stack has been replaced with VF Agent, a folder-based knowledge system that powers every planning, documentation, and implementation task inside the starter kit.

What lives under vf-agent/?

• Agents (vf-agent/agents/*.md) — Each role (orchestrator, product, PM, architect, SWE, QA, UX, etc.) has a dedicated file that defines its persona, activation instructions, and the commands/tasks it can run.
• Tasks + templates (vf-agent/tasks and vf-agent/templates) — Reusable instructions, checklists, and markdown templates for things like PRDs, stories, and docs. Treat them as the new “prompt + structure” combo; pick the task that matches what you need to do and follow the template.
• Checklists (vf-agent/checklists) — Step-by-step lists for common handoffs (e.g., releasing a feature, running a regression, validating docs revisions).
• Knowledge base (vf-agent/data/knowledge_base) — Organized into front-end, back-end, testing, and starter-docs directories. The starter-docs subfolder mirrors the docs section you are reading now with a reference doc for every feature, stack decision, and folder layout.
• Core config (vf-agent/core-config.yaml) — Dictates which knowledge files each agent loads, what the current project is, and where stories/PRDs live. It ensures every agent operates with the same context.

Why it matters to you

1. Consistent language – Every agent, task, and checklist references the same knowledge base (starter-docs/tech-stack.md, features-overview.md, etc.), so the explanations you read here match what the agents know.
2. Reusable guidance – When you need to write a new doc, plan a feature, or document an API, start by picking the appropriate task/template file instead of inventing the structure from scratch.
3. Traceable decisions – The knowledge base contains quick-reference articles for every feature, so you can always verify what the agents are training on and what dependencies exist.
4. Future-proofed workflow – As we ship new features, add a knowledge entry and update the relevant agent file so VF Agent stays aligned with the codebase.

Browse this directory whenever you need to understand the system behind the scenes—or copy one of the templates/tasks to keep your own docs and plans on-brand.