npx skills add smithery/hoodini --skill copilot-docs
hoodini/ai-agents-skills
copilot-docs
Configure GitHub Copilot with custom instructions. Use when setting up .github/copilot-instructions.md, customizing Copilot behavior, or creating repository-specific AI guidance. Triggers on Copilot instructions, copilot-instructions.md, GitHub Copilot config.
Installation
npx skills add hoodini/ai-agents-skills --skill copilot-docs
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsArchitect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…
402.8K installsAlso in this package
Other skills from hoodini/ai-agents-skills · top by installs.
npx skills add hoodini/ai-agents-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
master
Skill metadata
Parsed from SKILL.md frontmatter.
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md3,171 B -
docs
SUMMARY.md280 B
History
- First seen on skills.sh
- First recorded snapshot · 145 installs
SKILL.md
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).