app-guidelines-checklist

Validate repository compliance with API, architecture, and code-structure guidelines.

Updated Mar 28, 2025
One-click install
npx skills add https://github.com/gileck/app-template-ai --skill app-guidelines-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-guidelines-checklist
Source: https://github.com/gileck/app-template-ai/tree/main/.ai/skills/template/app-guidelines-checklist
Command: npx skills add https://github.com/gileck/app-template-ai --skill app-guidelines-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This checklist helps ensure that your application follows all established guidelines. Use this as a systematic approach to verifying compliance throughout the codebase.

Core Features & Use Cases

  • API & architecture audits: Verifies module structure, naming conventions, and re-exports for consistent APIs.
  • Feature and store guidelines: Ensures zustand stores, feature organization, and public API exports follow standards.
  • Routing, components, and UI: Checks route layout, server vs client boundaries, and shadcn/ui usage.
  • Final verification: Recommends running checks to guarantee zero TypeScript and lint errors.

Quick Start

Run the guidelines checklist against your repository and execute yarn checks to validate conformance.

Frequently Asked Questions about app-guidelines-checklist

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

FAQPage Schema
What is a repository guidelines checklist for code quality audits?

A repository guidelines checklist systematically verifies application compliance across API architecture, feature-based structure, and routing to ensure consistent code quality and standards adherence.

How do I validate YAML frontmatter and zustand stores in my project?

To validate YAML frontmatter and zustand stores, run a feature and store guidelines audit that checks public API exports and feature organization against established project standards.

How do I check feature-based folder structure and routing boundaries?

To check feature-based structure and routing boundaries, audit the route layout and verify server versus client component boundaries to ensure proper module separation and public API exports.

Does this guidelines checklist verify TypeScript and lint errors via yarn checks?

Yes, the guidelines checklist includes final verification by recommending yarn checks execution to guarantee zero TypeScript and lint errors across the audited repository.

Can I use this checklist for shadcn/ui component usage and architecture audits?

Yes, you can use this checklist for architecture audits as it specifically checks shadcn/ui usage, module structure, naming conventions, and re-exports for consistent APIs.

What are the limitations of using a manual checklist for code structure compliance?

A manual checklist for code structure compliance relies on systematic human verification and final yarn checks execution, meaning it does not automatically fix architectural inconsistencies or lint errors.