project-standards

Enforce repository documentation standards and track limitations via GitHub issues.

Updated Dec 25, 2025

Search Tags:#documentation #consistency #project standards #agent documentation #information routing #known limitations

Ready to run

npx skills add https://github.com/mourato/prisma --skill project-standards-mourato

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-standards
Source: https://github.com/mourato/prisma/tree/main/.agents/skills/project-standards
Command: npx skills add https://github.com/mourato/prisma --skill project-standards-mourato

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures consistent project documentation, tracks known limitations effectively, and maintains alignment with repository standards, preventing outdated information and redundant efforts.

Core Features & Use Cases

Limitation Tracking: Centralizes tracking of known limitations and trade-offs within GitHub issues, avoiding scattered markdown files.
Agent Documentation: Keeps AGENTS.md and related skills synchronized with current tool usage, script execution modes, and design system guidelines.
Information Routing: Provides a clear hierarchy for new knowledge, prioritizing skill absorption, followed by GitHub issues, and then deletion of stale content.

Quick Start

Use the project-standards skill to document a new known limitation by creating a GitHub issue.

Frequently Asked Questions about project-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track known limitations and trade-offs without scattering markdown files across a repository?▼

Limitation tracking is centralized by routing known trade-offs into GitHub issues instead of scattered markdown files. This prevents outdated information and eliminates redundant documentation efforts across the repository.

How do I keep agent documentation like AGENTS.md synchronized with current project states?▼

Agent documentation is kept synchronized by enforcing updates to AGENTS.md to reflect current tool usage, script execution modes, and design system guidelines. This ensures operational alignment and prevents outdated repository information.

What is the best way to route new information and knowledge in a software repository?▼

Information routing follows a clear hierarchy: new knowledge is prioritized for skill absorption, followed by GitHub issue creation, and finally the deletion of stale content. This maintains operational standards without redundancy.

Does this project standards approach enforce conventional commits and branch workflows?▼

Yes, enforcing consistent project documentation includes adherence to conventional commits, branch workflows, and UI quality gates. This ensures repository alignment and prevents operational deviations across the project lifecycle.

When should I not use markdown files to document a known project limitation?▼

Markdown files should be avoided for known limitations when centralized tracking via GitHub issues is available. Scattered markdown leads to outdated information and redundant efforts, whereas issues provide a single source of truth.