semantic-validation
Semantic Validation Skill
Purpose: Use GenAI to validate that documentation accurately reflects implementation, catching issues that structural validation misses.
When This Skill Activates
- Keywords:
Core Concepts
Overview
This skill provides comprehensive guidance on semantic validation. For detailed patterns and implementation examples, see the documentation files in docs/.
Key Topics:
- Detailed methodologies and best practices
- Implementation patterns and examples
- Common pitfalls and anti-patterns
- Cross-references to related skills
See: Documentation files in docs/ directory for complete details
Quick Reference
| Topic | Details |
|---|---|
| Detailed Guide 1 | docs/detailed-guide-1.md |
| Detailed Guide 2 | docs/detailed-guide-2.md |
| Detailed Guide 3 | docs/detailed-guide-3.md |
Progressive Disclosure
This skill uses progressive disclosure to prevent context bloat:
- Index (this file): High-level concepts and quick reference (<500 lines)
- Detailed docs:
docs/*.mdfiles with implementation details (loaded on-demand)
Available Documentation:
docs/detailed-guide-1.md- Detailed implementation guidedocs/detailed-guide-2.md- Detailed implementation guidedocs/detailed-guide-3.md- Detailed implementation guide
Cross-References
Related Skills:
- See PROJECT.md for complete skill dependencies
Related Tools:
- See documentation files for tool-specific guidance
Key Takeaways
- Research existing patterns before implementing
- Follow established best practices
- Refer to detailed documentation for implementation specifics
- Cross-reference related skills for comprehensive understanding
More from akaszubski/autonomous-dev
git-github
Git workflow and GitHub collaboration patterns including conventional commits, branch naming, PR workflow, and gh CLI usage. Use when creating commits, branches, or pull requests. TRIGGER when: git commit, branch, PR, pull request, merge, gh cli. DO NOT TRIGGER when: code implementation, testing, documentation without git operations.
26library-design-patterns
Two-tier design, progressive enhancement, non-blocking patterns, and security-first architecture for Python libraries. Use when creating or refactoring Python libraries. TRIGGER when: library design, module architecture, reusable component, two-tier. DO NOT TRIGGER when: simple scripts, config files, documentation-only changes.
26state-management-patterns
JSON persistence, atomic writes, file locking, crash recovery, and state versioning patterns. Use when implementing stateful libraries or features requiring persistent state. TRIGGER when: state persistence, atomic write, file locking, crash recovery, checkpoint. DO NOT TRIGGER when: stateless utilities, pure functions, config reads, documentation.
22code-review
10-point code review checklist covering correctness, tests, error handling, type hints, naming, security, and performance. Use when reviewing PRs or evaluating code quality. TRIGGER when: code review, PR review, review checklist, code quality check. DO NOT TRIGGER when: writing new code, debugging, refactoring without review context.
22api-design
REST API design best practices covering versioning, error handling, pagination, and OpenAPI documentation. Use when designing or implementing REST APIs or HTTP endpoints. TRIGGER when: API design, REST endpoint, HTTP route, OpenAPI, swagger, pagination. DO NOT TRIGGER when: internal library code, CLI tools, non-HTTP interfaces.
22skill-integration
Patterns for agent skill discovery, referencing, and composition using progressive disclosure architecture. Use when building agents, composing skills, or optimizing context usage. TRIGGER when: skill discovery, agent integration, skill composition, progressive disclosure. DO NOT TRIGGER when: implementing features, writing tests, documentation-only changes.
22