project-knowledge

Name: project-knowledge
Author: pavel-molyanov

241stars75forks

How to install project-knowledge?

pavel-molyanov/molyanov-ai-dev/project-knowledge

$npx -y skills add pavel-molyanov/molyanov-ai-dev --skill project-knowledge

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Project Knowledge
2
3	This skill provides access to project documentation that defines how this project works, how code should be written, and how features should be developed.
4
5	## When to use
6
7	Activate this skill when you need to:
8	- Understand project architecture, tech stack, and data model
9	- Learn coding patterns, git workflow, and testing approach
10	- Check deployment setup, monitoring, and operational procedures
11	- Apply UX guidelines and design system
12	- Make technical decisions aligned with project standards
13
14	## Core references
15
16	All documentation is in the `references/` folder:
17
18	- [project.md](references/project.md) - Project overview, purpose, target audience, core features, scope boundaries
19	- [architecture.md](references/architecture.md) - Tech stack, project structure, dependencies, external integrations, data flow, data model (schema, migrations, sensitive data)
20	- [patterns.md](references/patterns.md) - Project-specific coding conventions, git workflow (branching, testing, security gates), testing & verification methods, business rules
21	- [deployment.md](references/deployment.md) - Deployment platform, environment variables, CI/CD triggers, rollback, monitoring & observability (logging, error tracking, health checks)
22
23	## Optional references
24
25	- [ux-guidelines.md](references/ux-guidelines.md) - Interface language, tone of voice, domain glossary, text patterns, design system (only for projects with significant UI)
26	- {custom}.md - Domain-specific files added per project (e.g., vault.md, bot.md, mcp.md)
27
28	## How to use
29
30	Read specific guides as needed for your task:
31
32	- Starting feature development - read [project.md](references/project.md), [architecture.md](references/architecture.md), [patterns.md](references/patterns.md)
33	- Implementing database changes - read [architecture.md](references/architecture.md) (Data Model section)
34	- Working on UI/UX - read [ux-guidelines.md](references/ux-guidelines.md)
35	- Setting up deployment - read [deployment.md](references/deployment.md)
36	- Creating branches or PRs - read [patterns.md](references/patterns.md) (Git Workflow section)
37	- Investigating logs or errors - read [deployment.md](references/deployment.md) (Monitoring section)
38	- Working with domain logic - read [patterns.md](references/patterns.md) (Business Rules section)
39
40	All guides are maintained as single source of truth for project knowledge.

People who liked this also viewed

6 picks

Type

project-knowledge

241stars75forks

View on GitHub

How to install project-knowledge?

pavel-molyanov/molyanov-ai-dev/project-knowledge

$npx -y skills add pavel-molyanov/molyanov-ai-dev --skill project-knowledge

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Project Knowledge
2
3	This skill provides access to project documentation that defines how this project works, how code should be written, and how features should be developed.
4
5	## When to use
6
7	Activate this skill when you need to:
8	- Understand project architecture, tech stack, and data model
9	- Learn coding patterns, git workflow, and testing approach
10	- Check deployment setup, monitoring, and operational procedures
11	- Apply UX guidelines and design system
12	- Make technical decisions aligned with project standards
13
14	## Core references
15
16	All documentation is in the `references/` folder:
17
18	- [project.md](references/project.md) - Project overview, purpose, target audience, core features, scope boundaries
19	- [architecture.md](references/architecture.md) - Tech stack, project structure, dependencies, external integrations, data flow, data model (schema, migrations, sensitive data)
20	- [patterns.md](references/patterns.md) - Project-specific coding conventions, git workflow (branching, testing, security gates), testing & verification methods, business rules
21	- [deployment.md](references/deployment.md) - Deployment platform, environment variables, CI/CD triggers, rollback, monitoring & observability (logging, error tracking, health checks)
22
23	## Optional references
24
25	- [ux-guidelines.md](references/ux-guidelines.md) - Interface language, tone of voice, domain glossary, text patterns, design system (only for projects with significant UI)
26	- {custom}.md - Domain-specific files added per project (e.g., vault.md, bot.md, mcp.md)
27
28	## How to use
29
30	Read specific guides as needed for your task:
31
32	- Starting feature development - read [project.md](references/project.md), [architecture.md](references/architecture.md), [patterns.md](references/patterns.md)
33	- Implementing database changes - read [architecture.md](references/architecture.md) (Data Model section)
34	- Working on UI/UX - read [ux-guidelines.md](references/ux-guidelines.md)
35	- Setting up deployment - read [deployment.md](references/deployment.md)
36	- Creating branches or PRs - read [patterns.md](references/patterns.md) (Git Workflow section)
37	- Investigating logs or errors - read [deployment.md](references/deployment.md) (Monitoring section)
38	- Working with domain logic - read [patterns.md](references/patterns.md) (Business Rules section)
39
40	All guides are maintained as single source of truth for project knowledge.

People who liked this also viewed

6 picks

Type