Project Knowledge
This skill provides access to project documentation that defines how this project works, how code should be written, and how features should be developed.
When to use
Activate this skill when you need to:
- Understand project architecture, tech stack, and data model
- Learn coding patterns, git workflow, and testing approach
- Check deployment setup, monitoring, and operational procedures
- Apply UX guidelines and design system
- Make technical decisions aligned with project standards
Core references
All documentation is in the references/ folder:
- project.md - Project overview, purpose, target audience, core features, scope boundaries
- architecture.md - Tech stack, project structure, dependencies, external integrations, data flow, data model (schema, migrations, sensitive data)
- patterns.md - Project-specific coding conventions, git workflow (branching, testing, security gates), testing & verification methods, business rules, reference implementations
- deployment.md - Deployment platform, environment variables, CI/CD triggers, rollback, monitoring & observability (logging, error tracking, health checks)
Optional references
- ux-guidelines.md - Interface language, tone of voice, domain glossary, text patterns, design system (only for projects with significant UI)
- {custom}.md - Domain-specific files added per project (e.g., vault.md, bot.md, mcp.md)
How to use
Read specific guides as needed for your task:
- Starting feature development - read project.md, architecture.md, patterns.md
- Implementing database changes - read architecture.md (Data Model section)
- Working on UI/UX - read ux-guidelines.md
- Setting up deployment - read deployment.md
- Creating branches or PRs - read patterns.md (Git Workflow section)
- Investigating logs or errors - read deployment.md (Monitoring section)
- Working with domain logic - read patterns.md (Business Rules section)
All guides are maintained as single source of truth for project knowledge.
1---2name: project-knowledge3description: Use when you need information about this project's architecture, tech stack, coding patterns, data model, deployment setup, git workflow, or UX guidelines. Contains comprehensive project documentation including design decisions, technical specifications, and development standards.4---56# Project Knowledge78This skill provides access to project documentation that defines how this project works, how code should be written, and how features should be developed.910## When to use1112Activate this skill when you need to:13- Understand project architecture, tech stack, and data model14- Learn coding patterns, git workflow, and testing approach15- Check deployment setup, monitoring, and operational procedures16- Apply UX guidelines and design system17- Make technical decisions aligned with project standards1819## Core references2021All documentation is in the `references/` folder:2223- **[project.md](references/project.md)** - Project overview, purpose, target audience, core features, scope boundaries24- **[architecture.md](references/architecture.md)** - Tech stack, project structure, dependencies, external integrations, data flow, data model (schema, migrations, sensitive data)25- **[patterns.md](references/patterns.md)** - Project-specific coding conventions, git workflow (branching, testing, security gates), testing & verification methods, business rules, reference implementations26- **[deployment.md](references/deployment.md)** - Deployment platform, environment variables, CI/CD triggers, rollback, monitoring & observability (logging, error tracking, health checks)2728## Optional references2930- **[ux-guidelines.md](references/ux-guidelines.md)** - Interface language, tone of voice, domain glossary, text patterns, design system (only for projects with significant UI)31- **{custom}.md** - Domain-specific files added per project (e.g., vault.md, bot.md, mcp.md)3233## How to use3435Read specific guides as needed for your task:3637- Starting feature development - read [project.md](references/project.md), [architecture.md](references/architecture.md), [patterns.md](references/patterns.md)38- Implementing database changes - read [architecture.md](references/architecture.md) (Data Model section)39- Working on UI/UX - read [ux-guidelines.md](references/ux-guidelines.md)40- Setting up deployment - read [deployment.md](references/deployment.md)41- Creating branches or PRs - read [patterns.md](references/patterns.md) (Git Workflow section)42- Investigating logs or errors - read [deployment.md](references/deployment.md) (Monitoring section)43- Working with domain logic - read [patterns.md](references/patterns.md) (Business Rules section)4445All guides are maintained as single source of truth for project knowledge.