GitHub
test-quality-enforcement
Enforces test quality standards: behavior-focused tests, no property-only tests, round-trip JSON, comprehensive test blocks. Use when writing tests, reviewing test code, or ensuring test quality.
☆ 0View skill
AVRA-CADAVRA AI Skills
GitHub ↗Browse published AI skills maintained by AVRA-CADAVRA. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
60Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
experiment-testing-standards
Enforces experiment testing standards: real implementation testing, no simplified approximations, exact formula matching. Use when creating experiments, testing algorithms, or validating mathematical implementa...
☆ 0View skill
GitHub
integration-test-patterns
Guides integration test patterns: end-to-end workflows, cross-layer testing, real dependencies, no mocks unless approved. Use when writing integration tests, testing complete features, or validating system inte...
☆ 0View skill
GitHub
widget-test-patterns
Guides widget test patterns: BLoC testing, user interactions, state changes, material app setup. Use when writing widget tests, testing UI components, or validating widget behavior.
☆ 0View skill
GitHub
test-implementation-requirements
Enforces test implementation requirements: real dependencies, no mocks/stubs unless approved. Use when writing tests, reviewing test implementations, or ensuring tests use real functionality.
☆ 0View skill
GitHub
test-coverage-requirements
Enforces test coverage requirements: models (100%), repositories (95%), BLoCs (100%), use cases (100%), services (90%). Use when writing tests, reviewing test coverage, or ensuring adequate test coverage.
☆ 0View skill
GitHub
test-template-generation
Generates test templates: unit, widget, integration, service tests following project patterns. Use when creating new tests or ensuring tests follow project standards.
☆ 0View skill
GitHub
logging-standards-enforcement
Enforces mandatory logging standards using developer.log() instead of print(). Use when writing production code, reviewing code, or fixing logging violations.
☆ 0View skill
GitHub
file-organization-standards
Enforces file naming conventions, directory structure, one class per file, Clean Architecture layer placement. Use when creating new files, organizing code, or refactoring file structure.
☆ 0View skill
GitHub
linter-error-prevention
Enforces zero linter errors, common issue prevention, code cleanup. Use when writing code, reviewing code, or ensuring code quality standards.
☆ 0View skill
GitHub
code-documentation-standards
Enforces Dart doc comments for public APIs, parameter descriptions, usage examples. Use when writing public APIs, reviewing code, or ensuring documentation completeness.
☆ 0View skill
GitHub
spots-philosophy-integration
Ensures all code aligns with SPOTS core philosophy: "Doors, not badges", meaningful connections, real-world enhancement. Use when implementing features, reviewing code, or making architectural decisions to vali...
☆ 0View skill
GitHub
import-organization
Enforces import grouping (Dart SDK → Flutter → packages → relative), alphabetical order, unused import removal. Use when writing or reviewing code to ensure consistent import organization.
☆ 0View skill
GitHub
security-validation-checklist
Guides security validation checklist: Signal protocol security, encryption standards, authentication patterns, data protection. Use when validating security, reviewing security implementations, or ensuring secu...
☆ 0View skill
GitHub
privacy-protection-patterns
Enforces privacy protection patterns: anonymization, no PII in logs, secure data handling, GDPR compliance. Use when handling user data, implementing AI2AI, or ensuring privacy compliance.
☆ 0View skill
GitHub
status-query-handling
Guides status query handling protocol: find all related documents (plan, progress, status, complete), synthesize comprehensive answer. Use when user asks about status, progress, or completion.
☆ 0View skill
GitHub
expertise-system-implementation
Guides expertise system implementation: multi-path recognition, hierarchy (local → city → state → national), golden experts, visit quality. Use when implementing expertise calculations, expert recognition, or e...
☆ 0View skill
GitHub
plan-discovery-workflow
Guides plan discovery workflow: glob search, recency filtering, relevance assessment, priority reading. Use when starting new tasks, finding related plans, or gathering context.
☆ 0View skill
GitHub
hybrid-search-implementation
Guides hybrid search implementation: vector embeddings, keyword search, fusion algorithms, caching strategies. Use when implementing search, recommendation systems, or discovery features.
☆ 0View skill
GitHub
dependency-injection-getit
Guides GetIt dependency injection patterns for service registration. Use when creating new services, registering dependencies, or refactoring service architecture.
☆ 0View skill
GitHub
design-tokens-enforcement
Enforces design token usage (AppColors/AppTheme) instead of direct Colors.*. Use when writing UI code, reviewing widgets, or ensuring design consistency.
☆ 0View skill
GitHub
quantum-matching-algorithms
Guides quantum matching implementation: state calculations, compatibility formulas, quantum entanglement matching patterns. Use when implementing matching algorithms, compatibility calculations, or quantum stat...
☆ 0View skill
GitHub
ai2ai-learning-service
Guides AI2AI learning service implementation: personality spectrum, compatibility calculations, learning methods, anonymous data exchange. Use when implementing AI2AI learning, personality evolution, or peer le...
☆ 0View skill
GitHub
business-partnership-patterns
Guides business partnership implementation: multi-party events, revenue sharing, vibe matching, pre-event agreements. Use when implementing partnerships, event collaborations, or revenue sharing features.
☆ 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.