project-guidelines-example

Name: project-guidelines-example
Availability: InStock
Author: danielkhigay

Define reusable project guidelines templates with frontmatter and Markdown structure.

Updated Feb 19, 2026

Search Tags:#architecture #templates #documentation #deployment #frontend-backend #code-patterns #project-guidelines

Ready to run

npx skills add https://github.com/danielkhigay/gaz --skill project-guidelines-example-danielkhigay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-guidelines-example
Source: https://github.com/danielkhigay/gaz/tree/main/.claude/skills/archived/project-guidelines-example
Command: npx skills add https://github.com/danielkhigay/gaz --skill project-guidelines-example-danielkhigay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a reusable template to standardize how teams capture project guidelines, including architecture, file structure, testing, and deployment practices, reducing onboarding time and ambiguity.

Core Features & Use Cases

Architecture overview templates for frontend and backend stacks
File structure documentation and code patterns
Testing and deployment guidance
Governance and collaboration workflow references

Quick Start

Replace placeholders with your project's details to customize the guidelines template.

Frequently Asked Questions about project-guidelines-example

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

FAQPage Schema

How do I create standardized project guidelines for frontend and backend architecture?▼

To create standardized project guidelines, use a reusable template that documents architecture, file structure, and workflows for frontend-backend stacks. This enforces documentation quality by requiring a frontmatter with name and description alongside a detailed Markdown guide.

What should be included in engineering project documentation templates?▼

Engineering project documentation templates should include architecture overviews, file structure documentation, code patterns, testing and deployment guidance, and governance workflow references to reduce onboarding time and ambiguity for new team members.

How do I standardize deployment and testing practices across multiple projects?▼

Standardize deployment and testing practices by applying a reusable guidelines template that provides a copy-ready blueprint for new projects. This ensures consistent documentation of workflows across project-enabled contexts and teams.

Can I customize a project guidelines template for my team's specific code patterns?▼

Yes, you can customize the project guidelines template by replacing placeholders with your project's specific details. This allows you to tailor architecture overviews, code patterns, and governance references to match your team's workflows.

What is the best way to document project governance and collaboration workflows?▼

The best way to document project governance and collaboration workflows is using a standardized template that captures governance references alongside architecture and deployment practices, providing a complete blueprint that reduces ambiguity for all team members.

Does this project guidelines template support optional scripts and reference assets?▼

Yes, the project guidelines template supports optional scripts, references, and assets managed through the skill, while enforcing mandatory structure through a frontmatter with name and description and a detailed Markdown guide.