documentation-fundamentals
Auto-invoke when reviewing README files, JSDoc comments, or inline documentation. Enforces "WHY not WHAT" principle.
Browse published AI skills maintained by DanielPodolsky. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
40Repository stars across indexed skills
5,703Repository forks
413Average repository stars per indexed skill
143Repository stars may repeat across skills from the same repository.
Auto-invoke when reviewing README files, JSDoc comments, or inline documentation. Enforces "WHY not WHAT" principle.
Verify performance implications were considered and no obvious anti-patterns exist. Issues result in WARNINGS.
Verify security considerations were addressed before shipping. Issues result in WARNINGS that strongly recommend fixing.
Auto-invoke for general code quality review. Enforces naming conventions, function size, DRY principles, SOLID principles, and code organization.
Verify errors are handled gracefully with meaningful user feedback. Issues result in WARNINGS.
Auto-invoke when reviewing test files or discussing testing strategy. Enforces testing pyramid, strategic coverage, and stack-appropriate frameworks.
Auto-invoke when reviewing schema design, database queries, ORM usage, or migrations. Enforces normalization, indexing awareness, query optimization, and migration safety.
Auto-invoke when reviewing React, Vue, or frontend component code. Enforces component architecture, state management patterns, and UI best practices.
Auto-invoke when reviewing HTML head, meta tags, or Next.js page components. Enforces semantic HTML and search optimization.
Verify code quality standards are met - naming, structure, DRY principles. Issues result in SUGGESTIONS for improvement.
Auto-invoke when reviewing authentication, authorization, input handling, data exposure, or any user-facing code. Enforces OWASP top 10 awareness and security-first thinking.
Auto-invoke after task completion to generate powerful resume bullet points from completed work.
Verify the junior can explain and defend every line of code they wrote. This gate BLOCKS completion if failed.
Auto-invoke when reviewing try/catch blocks, API error responses, async operations, or user feedback patterns. Enforces graceful degradation and meaningful error messages.
Gate 6 - Verify tests exist and cover critical paths. Issues result in WARNINGS (encourages tests, doesn't block).
Auto-invoke after task completion to extract interview-ready STAR stories from completed work.
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.