GitHub
typescript
TypeScript strict patterns and best practices. Trigger: When implementing or refactoring TypeScript in .ts/.tsx (types, interfaces, generics, const maps, type guards, removing any, tightening unknown).
☆ 0View skill
Documentation AI Skills
Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Categories: Documentation
Documentation Clear filters
Browse skills
GitHub
logger
Structured logging and reporting system for development work sessions. Trigger: Completing development tasks, generating session reports, documenting changes.
☆ 0View skill
GitHub
prettier
Code formatting with Prettier for TypeScript/NestJS projects. Trigger: After editing/creating files, before committing code, ensuring code style consistency.
☆ 0View skill
GitHub
aurora-schema
Aurora YAML schema analysis and editing. Validates field names, descriptions, types, and module semantics following DDD best practices. Trigger: When analyzing or editing *.aurora.yaml files, improving field na...
☆ 0View skill
GitHub
aurora-criteria
Aurora Criteria Pattern - Complete guide for QueryStatement usage in Aurora/NestJS. Trigger: When implementing queries, filters, searches, pagination, or complex data retrieval.
☆ 0View skill
GitHub
conventional-commits
Git commit management following Conventional Commits specification for Aurora projects. Trigger: When creating commits, analyzing git history, or reviewing commit messages.
☆ 0View skill
GitHub
aurora-cli
Run Aurora CLI commands to generate/regenerate modules, add packages, or create projects. Trigger: When user asks to regenerate code, load module, add package, or create new Aurora project.
☆ 0View skill
GitHub
postgresql
PostgreSQL expert skill - Advanced SQL, extensions, data types, indexing, performance tuning, and PostgreSQL-specific features. Trigger: When writing SQL queries, designing schemas, optimizing performance, usin...
☆ 0View skill
GitHub
aurora-project-structure
Provides structured information about the Aurora/NestJS project folder hierarchy, explaining the purpose and responsibility of each directory and key files. Trigger: When user asks about project structure, fold...
☆ 0View skill
GitHub
supertest-nestjs
Supertest patterns and best practices for NestJS e2e API testing. Trigger: When writing e2e tests, testing HTTP endpoints, or testing authentication flows in NestJS.
☆ 0View skill
GitHub
feature-scaffolding
BoxLogの新しいFeatureモジュールを作成。stores, hooks, components, types の統一構造を生成。
☆ 0View skill
GitHub
trpc-router-creating
BoxLogのtRPC v11ルーターを作成。サービス層分離、Zodバリデーション、エラーハンドリングを適用。
☆ 0View skill
GitHub
releasing
BoxLogのリリース作業をガイド。バージョン決定、重複チェック、リリースノート作成、タグ付けまでの全プロセスを支援。
☆ 0View skill
GitHub
store-creating
BoxLogのZustand storeを作成。devtools, persist, 型安全なパターンを適用。
☆ 0View skill
GitHub
smarthomehq-architect
SmartHomeHQ repo assistant for a HomeKit-first smart home (Home Assistant hub on UTM Mac mini, Scrypted cameras, Homebridge niche integrations). Use for inventory, ownership decisions, HomeKit exposure hygiene,...
☆ 0View skill
GitHub
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before as...
☆ 0View skill
GitHub
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
☆ 0View skill
GitHub
test-driven-development
Use when implementing any feature or bugfix in C#/.NET before writing implementation code; applies to gRPC services, EF Core data access, and Blazor components
☆ 0View skill
GitHub
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
☆ 0View skill
GitHub
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
☆ 0View skill
GitHub
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
☆ 0View skill
GitHub
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior in C#/.NET code before proposing fixes; applies to gRPC services, EF Core queries, async operations, and build failures
☆ 0View skill
GitHub
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
☆ 0View skill
GitHub
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.