Project Knowledge
Developmentproject-knowledgeProject Knowledge is an Agent Skill for development published in the lesovsky/noisia repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/lesovsky/noisia/blob/HEAD/.claude/skills/project-knowledge/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/project-knowledge, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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.