What is project-guidelines-example?

An example template for documenting project-specific development rules. It shows how to record a project's architecture, tools, file structure, testing expectations, and deployment process.

Creating project instructions, documenting a codebase's technology choices and workflow, and describing its testing and deployment requirements.

Without shared project guidance, contributors may make inconsistent technical decisions or miss required checks. A project guide gives agents and developers a common reference.

project-guidelines-example — Skill by Jamkris/everything-gemini-code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Jamkris/everything-gemini-code --skill project-guidelines-example

Clone the repo

git clone --depth 1 https://github.com/Jamkris/everything-gemini-code

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/project-guidelines-example/github.svg)](https://agentmods.dev/skills/jamkris/everything-gemini-code/project-guidelines-example)

Your own site

<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/project-guidelines-example"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/project-guidelines-example/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/project-guidelines-example"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/project-guidelines-example.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,163 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 84% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.02163
Opus 5.5	$0.00005	$0.00865
Sonnet 5.5	$0.00003	$0.00433
Haiku 4.5	$0.00001	$0.00216

Measured 1mo ago against content hash 181ba8c4556f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

project-guidelines-example scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

84% identical to cc-skill-project-guidelines-example — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/project-guidelines-example/SKILL.md · 351 lines

How it starts

The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 - 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: Gemini 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                                       │
└─────────────────────────────────────────────────────────────┘
                              │
              ┌───────────────┼───────────────┐
              ▼               ▼               ▼
        ┌──────────┐   ┌──────────┐   ┌──────────┐
        │ Supabase │   │  Gemini  │   │  Redis   │
        │ Database │   │   API    │   │  Cache   │
        └──────────┘   └──────────┘   └──────────┘

File Structure

project/
├── frontend/
│   └── src/
│       ├── app/              # Next.js app router pages
│       │   ├── api/          # API routes
│       │   ├── (auth)/       # Auth-protected routes
│       │   └── workspace/    # Main app workspace
│       ├── components/       # React components
│       │   ├── ui/           # Base UI components
│       │   ├── forms/        # Form components
│       │   └── layouts/      # Layout components
│       ├── hooks/            # Custom React hooks
│       ├── lib/              # Utilities
│       ├── types/            # TypeScript definitions
│       └── config/           # Configuration
│
├── backend/
│   ├── routers/              # FastAPI route handlers
│   ├── models.py             # Pydantic models
│   ├── main.py               # FastAPI app entry
│   ├── auth_system.py        # Authentication
│   ├── database.py           # Database operations
│   ├── services/             # Business logic
│   └── tests/                # pytest tests
│
├── deploy/                   # Deployment configs
├── docs/                     # Documentation
└── scripts/                  # Utility scripts

Read the full file on GitHub · 351 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 351 lines · 13 tokens per session scan A 181ba8c4556f

Subscribe to this mod's changes

project-guidelines-example is a skill published in the GitHub repository Jamkris/everything-gemini-code (91 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 2,163 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to cc-skill-project-guidelines-example, differing in 22 lines, and is treated as a copy.

Project management ai-agents antigravity developer-tools gemini-cli gemini-cli-extension gemini-cli-skills

beads

Git-backed issue tracker for multi-session work with dependencies and persistent memory across conversation compaction. Use when work spans sessions, has blockers, or needs context recovery after compaction.

thoreinstein/gemini-beads · 38 tokens

track-creation

Create new Conductor tracks with spec, plan, and metadata files. Bundles all templates needed for track creation. Use when starting a new feature track via /omg:track or when manually creating tracks.

richardcb/oh-my-gemini · 48 tokens

projectflow-execute

Execute, resume, inspect, skip, or redo ProjectFlow DAG projects through the projectflow MCP server. Use when the user supplies a ProjectFlow JSON graph, asks to run work by dependency order, wants cross-session progress recovery, or requests ProjectFlow status changes.

wjmiracle/projectflow-dag-mcp · 58 tokens

project-guidelines-example