Skill Creator
LerianStudio
56 published skills · 1,400 GitHub stars across the catalog. View on GitHub ↗
dev-cycle
Main orchestrator for the 6-gate development cycle system. Loads tasks/subtasksfrom PM team output and executes through implementation, devops, SRE, testing, review,and validation gates with state persistence and metrics collection.
dev-devops
Gate 1 of the development cycle. Creates/updates Docker configuration,docker-compose setup, and environment variables for local developmentand deployment readiness.
dev-feedback-loop
Development cycle feedback system - calculates assertiveness scores, analyzes promptquality for all agents executed, aggregates cycle metrics, performs root cause analysison failures, and generates improvement reports to docs/feedbacks/cycle-{date}/.
dev-implementation
Gate 0 of the development cycle. Executes code implementation using the appropriatespecialized agent based on task content and project language. Handles TDD workflowwith RED-GREEN phases. Follows project standards defined in docs/PROJECT_RULES.md.
dev-refactor
Analyzes codebase against standards and generates refactoring tasks for dev-cycle.
dev-sre
Gate 2 of the development cycle. VALIDATES that observability was correctly implementedby developers. Does NOT implement observability code - only validates it.
dev-testing
Gate 3 of development cycle - ensures unit test coverage meets threshold (85%+)for all acceptance criteria using TDD methodology.
dev-validation
Development cycle validation gate (Gate 5) - validates all acceptance criteria are metand requires explicit user approval before completion.
using-dev-team
7 specialist developer agents for backend (Go/TypeScript), DevOps, frontend,design, QA, and SRE. Dispatch when you need deep technology expertise.
regulatory-templates-gate1
Gate 1 sub-skill - performs regulatory compliance analysis and field mappingfrom template specifications.
regulatory-templates-gate2
Gate 2 sub-skill - validates uncertain mappings from Gate 1 and confirmsall field specifications through testing.
regulatory-templates-gate3
Gate 3 sub-skill - generates complete .tpl template file with all validatedmappings from Gates 1-2.
regulatory-templates-setup
Initial setup sub-skill - handles template selection and context initializationfor the 3-gate regulatory workflow.
regulatory-templates
3-gate regulatory template orchestrator - manages setup, Gate 1 (analysis),Gate 2 (validation), Gate 3 (generation) for BACEN/RFB compliance.
using-finops-team
2 FinOps agents for Brazilian financial regulatory compliance (BACEN, RFB,Open Banking). Dispatch for compliance analysis or template generation.
pre-dev-api-design
Gate 4: API contracts document - defines component interfaces and data contractsbefore protocol/technology selection. Large Track only.
pre-dev-data-model
Gate 5: Data structures document - defines entities, relationships, and ownershipbefore database technology selection. Large Track only.
pre-dev-dependency-map
Gate 6: Technology choices document - explicit, versioned, validated technologyselections with justifications. Large Track only. HARD BLOCK: Must load Ring Standardsand PROJECT_RULES.md before proceeding.
pre-dev-feature-map
Gate 2: Feature relationship map - visualizes feature landscape, groupings,and interactions at business level before technical architecture.
pre-dev-prd-creation
Gate 1: Business requirements document - defines WHAT/WHY before HOW.Creates PRD with problem definition, user stories, success metrics.
pre-dev-research
Gate 0 research phase for pre-dev workflow. Dispatches 3 parallel research agentsto gather codebase patterns, external best practices, and framework documentationBEFORE creating PRD/TRD. Outputs research.md with file:line references.
pre-dev-subtask-creation
Gate 8: Zero-context implementation steps - 2-5 minute atomic subtasks withcomplete code, exact commands, TDD pattern. Large Track only.
pre-dev-task-breakdown
Gate 7: Implementation tasks - value-driven decomposition into working incrementsthat deliver measurable user value.
pre-dev-trd-creation
Gate 3: Technical architecture document - defines HOW/WHERE with technology-agnosticpatterns before concrete implementation choices.