generar-tech-design
Generate the Technical Design Document + ADRs (MADR format) + acceptance criteria for a project, interviewing the user decision by decision starting from…
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-26 00:15
37,987 results
Generate the Technical Design Document + ADRs (MADR format) + acceptance criteria for a project, interviewing the user decision by decision starting from…
Project-specific skill template covering architecture, patterns, testing, and deployment guidance.
Opinionated house conventions for NestJS backends — module boundaries and layering, provider wiring and injection scopes, guards/interceptors/pipes/filters,…
Generate CRUD code based on the RuoYi framework specifications. Use this skill when the user needs to generate backend Java code (entity class, Mapper, Service, Controller), frontend Vue code (list page, API wrapper), MyBatis XML mapping file, or menu initialization SQL for a data table. Applicable to: creating new modules, adding business functions, generating code based on table structures, and other scenarios.
Ascend Transformer Boost (ATB) Core Skills Set Index (Index Skill). Integrates 8 core skills: CANN installation and deployment, ATB test framework compilation, ATB→ACLNN operator replacement design document generation, ATB→ACLNN operator migration, covering the full Ascend NPU development chain.
Design, implement, and review Roblox DataStore persistence. Use for save/load schemas, migrations, autosave, retries, player leave saves, server shutdown…
Strapi v5 plugin development expert. Use for building, refactoring, or revamping plugins, custom APIs, admin panel extensions, Document Service API usage,…
This skill helps users extract structured product listings from Amazon, including titles, ASINs, prices, ratings, and specifications. Use this skill when users…
Use when selecting Bevy 0.19 Cargo features such as `2d`/`3d`/`ui`/`audio`, composing `3d_bevy_render` or API-only `3d_api`, building headless with…
Stage 2 of the feature flow—write code in the order given by {slug}-design.md, then report completion to the user for review in a unified format. The prerequisite is that {slug}-design.md has been approved (a standard design includes test design, or a fastforward design includes acceptance criteria), and that in the same directory there is…
When fixing a bug, enter this sub-process—take "discovered a problem" from a verbal description to a closed loop of verified fix, leaving three files in between: problem report, root cause analysis, and fix record. This process adds a layer of buffering between "seeing the problem" and "changing the code," avoiding several common ways of going off the rails: the problem description in your head disappears once the fix is done, you act without analyzing the root cause and only change the surface, the scope of the fix sprawls and can't be traced, and after the fix there's no verification so you don't know whether you fixed it right. This skill only does routing, ...
Stage 2 of the issue flow—read the issue report + read the code to find the real root cause and assess fix risk, then give the user 2-3 fix options to let them decide. This stage is **not about starting to change code**—after analysis, show the user the conclusion first, and only enter stage 3 after the user confirms the approach. Prerequisite: easysdd-issue-report is complete. Trigger scenarios: user says "analyze this…
Phase 1 of the issue workflow—turn the problem in the user's head into a reproducible, traceable {slug}-report.md through conversation. Here the AI only asks "what did you see, how do you reproduce it, what should happen instead" and does not guess the root cause for the user (that is phase 2's job). At the same time, this phase is the only formal decision point for deciding whether to take the fast track or the standard path: based on the user's description, first read the relevant code, and if it can be pinpointed at a glance and the change is small, directly tell them to use…
Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code,…
Comprehensive Go/Golang development best practices covering project structure, error handling, concurrency, testing, performance optimization, and code…
Run after making Docyrus API changes to catch bugs, performance issues, and code quality problems. Use when implementing or modifying code that uses Docyrus…
Lombok annotations and best practices for Java 21+ projects. Use when reducing boilerplate, configuring builders, or choosing between Lombok and Records.
Go application architecture with net/http 1.22+ routing, project structure patterns, graceful shutdown, and dependency injection. Use when building Go web…
Block automated bots from scraping your catalog, scalping limited inventory, and abusing checkout flows using CAPTCHA and behavioral detection
Commits relevant changes, merges the remote base when needed, pushes the current pull-request branch, and refreshes stale PR metadata. Use when asked to update…
Operate any desktop software using a "screenshot + coordinate grid" approach: take grid-overlaid screenshots, let any multimodal large model read the target's coordinate numbers, then call click/input/keypress and other APIs to simulate human visual operation of software. You can also record an operation once and distill it into a reusable scenario template for direct reuse next time. Does not rely on the target software providing an API or CLI. Use when the following situations occur: - Automating operations on Windows...
GitLab group operations via API. ALWAYS use this skill when user wants to: (1) list/view groups, (2) create/update/delete groups, (3) manage group members, (4)…
Hedera Token Service (HTS) smart contract development. Use when creating, managing, or interacting with Hedera-native tokens via Solidity contracts. Triggers…
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.