Agent skill · Design & Presentation

project-guidelines-example

Example template for project-specific skill files covering architecture, patterns, testing, and deployment.

vibeevalgithub.com/vibeevalGitHub ↗
claude-codeMIT
Install
npx skills add vibeeval/vibecosystem --skill project-guidelines-example --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/project-guidelines-example/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 521
Language: C#

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Project Guidelines Skill (Example) This is an example of a project-specific skill. Use this as a template for your own projects. Based on a real production application: [Zenith](https://zenith.chat) - AI-powered customer discovery platform. --- ## When to Use Reference this skill when working on the specific project it's designed for. Project skills contain: - Architecture overview - File structure - Code patterns - Testing requirements - Deployment workflow --- ## Architecture Overview **Tech Stack:** - **Frontend**: Next.js 15 (App Router), TypeScript, React - **Backend**: FastAPI (Python), Pydantic models - **Database**: Supabase (PostgreSQL) - **AI**: Claude API with tool calling and structured output - **Deployment**: Google Cloud Run - **Testing**: Playwright (E2E), pytest (backend), React Testing Library **Services:** ``` ┌─────────────────────────────────────────────────────────────┐ │ Frontend │ │ Next.js 15 + TypeScript + TailwindCSS │ │ Deployed: Vercel / Cloud Run │ └─────────────────────────────────────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────────────────────────┐ │ Backend │ │ FastAPI + Python 3.11 + Pydantic │ │ Deployed: Cloud Run │

What's inside
Steps it walks through
  1. When to Use
  2. Architecture Overview
  3. File Structure
  4. Code Patterns
  5. API Response Format (FastAPI)
  6. Frontend API Calls (TypeScript)
  7. Claude AI Integration (Structured Output)
  8. Custom Hooks (React)
  9. Testing Requirements
  10. Backend (pytest)
  11. Frontend (React Testing Library)
  12. Deployment Workflow
  13. Pre-Deployment Checklist
  14. Deployment Commands
Commands it runs
Run all tests
poetry run pytest tests/
Run with coverage
poetry run pytest tests/ --cov=. --cov-report=html
Run specific test file
poetry run pytest tests/test_auth.py -v
Run tests
npm run test
npm run test -- --coverage
Run E2E tests
More from vibecosystem
All skills →
frontend-devFull-stack frontend development combining premium UI design, cinematic animations, AI-generated…Frontendminimax-pdfUse this skill when visual quality and design identity matter for a PDF. CREATE (generate from…Code Review & Qualitycontinuous-learning-v2Instinct-based learning system that observes sessions via hooks, creates atomic instincts with…Othercontinuous-learningAutomatically extract reusable patterns from Claude Code sessions and save them as learned skills…AI & Agentsminimax-docxProfessional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three…Content & Marketingminimax-xlsxOpen, create, read, analyze, edit, or validate Excel/spreadsheet files (.xlsx, .xlsm, .csv, .tsv).…Data & Analytics
About this skill
What does the project-guidelines-example skill do?

Example template for project-specific skill files covering architecture, patterns, testing, and deployment.

How do I install it?

Run `npx skills add vibeeval/vibecosystem --skill project-guidelines-example --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.