Loading...
Loading...
Found 56 Skills
Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.
Use when you need maximum precision on a critical task — production deployments, security-sensitive code, financial calculations, or any work where mistakes are unacceptable.
Use when working with AdonisJS Lucid ORM and SQL layer: database configuration, migrations, schema generation, schema classes, models, CRUD operations, model query builder, query scopes, hooks, serialization, relationships, transactions, pagination, debugging, validation rules, model factories, seeders, or database query builders. Trigger for tasks involving @adonisjs/lucid, database/schema.ts, app/models, database/migrations, database/factories, database/seeders, db service queries, Lucid relationships, or model behavior.
Use when the workflow feels over-engineered, has premature optimizations, unnecessary abstraction layers, or complexity beyond actual requirements.
Evaluate UI/flows from cognitive load, error prevention, and accessibility perspectives. Apply when reviewing UX, discussing user confusion, high drop-off, or form usability issues.
Use when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.
Use when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.
Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
Receive context from parent, child, or sibling session
Use when deploying to production, handling sensitive data, or the workflow needs safety constraints, input validation, and security boundaries.
Use when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.
Use the `date` command via Bash tool whenever you or the user mention time, dates, or temporal concepts. Verify current date/time before ANY temporal response, as environment context may be outdated. Parse expressions like "tomorrow", "next week", "3 days", "in 2 weeks", "next Monday at 3pm". Proactively invoke for deadlines, schedules, time-sensitive tasks, week numbers, or any date/time reference.