Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
hoodini avatar

Copilot Docs

  • 132 installs
  • 262 repo stars
  • Updated July 11, 2026
  • hoodini/ai-agents-skills

Author repository docs, inline comments, and skill readmes structured so GitHub Copilot and Claude Code retrieve accurate patterns, APIs, and examples during codegen.

About

Skill for writing Copilot-friendly project documentation: structured READMEs, focused module docs, and example-driven comments that improve AI-assisted coding. Helps teams building agents or SaaS repos keep GitHub Copilot and similar tools aligned with actual APIs, folder layout, and team conventions.

  • Doc layouts optimized for Copilot context retrieval
  • Module-level examples assistants can mirror
  • Consistent API and pattern descriptions
  • Reduces hallucinated imports and wrong APIs
  • Keeps human and AI readers on same conventions

Copilot Docs by the numbers

  • 132 all-time installs (skills.sh)
  • +6 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #599 of 1,879 Documentation skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/hoodini/ai-agents-skills --skill copilot-docs

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs132
repo stars262
Last updatedJuly 11, 2026
Repositoryhoodini/ai-agents-skills

What it does

Author repository docs, inline comments, and skill readmes structured so GitHub Copilot and Claude Code retrieve accurate patterns, APIs, and examples during codegen.

Files

SKILL.mdMarkdownGitHub ↗

GitHub Copilot Custom Instructions

Configure repository-specific instructions for GitHub Copilot.

Quick Start

Create .github/copilot-instructions.md in your repository:

# Copilot Instructions

## Code Style
- Use TypeScript with strict mode
- Prefer functional components with hooks
- Use Tailwind CSS for styling

## Project Context
This is a Next.js 14 app using the App Router.
API routes are in `app/api/`.

Effective Patterns

Project Context

# Project Context

## Tech Stack
- Next.js 14 with App Router
- TypeScript 5.3+
- Tailwind CSS 3.4
- Prisma ORM with PostgreSQL

## Architecture
- `app/` - Next.js App Router pages and API routes
- `components/` - React components
- `lib/` - Utility functions and shared code
- `prisma/` - Database schema and migrations

Code Standards

# Code Standards

## TypeScript
- Enable strict mode
- Prefer `interface` over `type` for object shapes
- Use explicit return types on functions

## React
- Use functional components exclusively
- Prefer named exports
- Extract hooks to `hooks/` directory

## Error Handling
- Use Result pattern for fallible operations
- Always handle async errors with try/catch
- Log errors with structured format

Naming Conventions

# Naming Conventions

## Files
- Components: PascalCase (Button.tsx)
- Utilities: camelCase (formatDate.ts)
- Constants: SCREAMING_SNAKE_CASE

## Code
- Boolean variables: is*, has*, should* prefix
- Event handlers: handle* prefix (handleClick)
- Async functions: *Async suffix

Testing

# Testing Guidelines

## Unit Tests
- Use Vitest for unit testing
- Place tests next to source files (*.test.ts)
- Mock external dependencies

## Test Patterns

describe('Component', () => { it('should render correctly', () => { // Arrange, Act, Assert pattern }); });

API Patterns

# API Patterns

## Route Handlers

// Standard response format return NextResponse.json({ data: result, error: null, meta: { timestamp: Date.now() } });

// Error response return NextResponse.json( { data: null, error: { code: 'NOT_FOUND', message: '...' } }, { status: 404 } );


## Validation
- Use Zod for request validation
- Validate early, fail fast

Do's and Don'ts

# Guidelines

## Do
- Write self-documenting code
- Add JSDoc comments for public APIs
- Use meaningful variable names

## Don't
- Use `any` type
- Leave console.log in production code
- Commit sensitive data

File Location

The file must be at .github/copilot-instructions.md (not in root).

Resources

  • GitHub Docs: https://docs.github.com/en/copilot/customizing-copilot/adding-custom-instructions-for-github-copilot
  • VS Code Copilot: https://code.visualstudio.com/docs/copilot/copilot-customization

Related skills

Documentationdocsintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.