Menú
SkillsMP ha recopilado 33 skills de boparaiamrit/skills-by-amrit. Abre una skill para revisar su origen y sus detalles.
Mostrando 33 de 33 skills recopiladas.
Use when porting any module from a Next.js (React) app to a Nuxt 4 (Vue 3) production app backed by NestJS. User provides module name and three repo paths. Covers submodule analysis, backend verification, feature inventory, sidebar registration,…
Idioma del texto original: inglés
Use as the master reference for all core principles, anti-hallucination protocol, severity framework, and skill activation rules. Every other skill inherits from this. Read this first in any new session.
Idioma del texto original: inglés
Use when creating new skills for the skills library. Defines the structure, format, quality standards, and testing requirements for new skills.
Idioma del texto original: inglés
Multi-agent council using real subagent spawning (Task() tool), deterministic CLI state management, and file-based handoffs. Orchestrator stays lean while specialists execute in fresh contexts.
Idioma del texto original: inglés
Use when you have a spec or requirements for a multi-step task and need to create a detailed implementation plan before touching code.
Idioma del texto original: inglés
Use when you have a detailed implementation plan and need to execute it task by task with deviation handling, checkpoints, and atomic commits.
Idioma del texto original: inglés
Automated persistent memory system for AI agents — captures decisions, context, and learnings across sessions using file-based protocols. Works in Antigravity, Cursor, Claude Code, and any agent that can read/write files.
Idioma del texto original: inglés
Use when auditing database schema, migrations, data integrity, query patterns, or when asked about database architecture. Covers schema design, indexing strategy (including high-volume tables), migrations, constraints, query optimization, and data…
Idioma del texto original: inglés
Use when the frontend needs a visual overhaul — redesign with uniformity. Exhaustively audits the existing frontend (design tokens, components, layouts, typography, color, spacing, animations), maps every backend API and data model, identifies UI/UX problems,…
Idioma del texto original: inglés
Use when adding any new code, feature, component, or endpoint to an existing codebase. Enforces pattern uniformity by requiring observation of existing code patterns before writing, matching them exactly, and double-verifying conformity. Covers frontend,…
Idioma del texto original: inglés
Use when auditing UI for accessibility, WCAG compliance, keyboard navigation, screen reader support, or when building inclusive interfaces.
Idioma del texto original: inglés
Use when designing, reviewing, or auditing APIs — REST, GraphQL, RPC, WebSocket. Covers endpoint design, request/response contracts, versioning, error handling, pagination, rate limiting, and documentation.
Idioma del texto original: inglés
Use when asked to audit, evaluate, or understand a codebase's architecture. Covers structure, patterns, coupling, cohesion, and architectural drift. Use after codebase-mapping for full context.
Idioma del texto original: inglés
Use before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores intent, requirements, and design before implementation.
Idioma del texto original: inglés
Use when auditing build pipelines, deployment processes, CI/CD configuration, environment management, or release workflows. Covers build reliability, deployment safety, rollback capability, secrets management, and environment parity.
Idioma del texto original: inglés
Use when completing tasks, implementing features, before merging, or when asked to review code. Systematic review process covering correctness, security, performance, and maintainability.
Idioma del texto original: inglés
Use when first encountering a codebase, onboarding to a project, or needing to understand system structure before auditing or modifying. Creates a mental model of the system before any changes.
Idioma del texto original: inglés
Use when reviewing project dependencies, investigating supply chain security, checking for outdated packages, or evaluating new dependencies to add.
Idioma del texto original: inglés
Use when auditing frontend code — component architecture, state management, accessibility, design system consistency, bundle size, and rendering performance. Framework-agnostic with specific guidance for React, Vue, Svelte, and vanilla JS.
Idioma del texto original: inglés
Use when performing any git operations — branching, committing, merging, rebasing, resolving conflicts. Ensures clean history, atomic commits, and proper branch management.
Idioma del texto original: inglés
Use during production incidents — outages, security breaches, data corruption, performance degradation. Provides structured triage, mitigation, resolution, and post-mortem processes.
Idioma del texto original: inglés
Use when auditing logging, monitoring, alerting, tracing, or metrics. Covers structured logging, error tracking, health checks, dashboards, distributed tracing, and incident detection capabilities.
Idioma del texto original: inglés
Use when investigating slow responses, high resource usage, scaling concerns, or when asked about performance. Covers database queries (N+1), memory, CPU, rendering, caching, and load patterns.
Idioma del texto original: inglés
Use when changing existing code — restructuring, renaming, extracting, inlining, or migrating. Ensures behavior is preserved through methodical, test-backed transformations.
Idioma del texto original: inglés
Use when asked about security, when auditing a codebase, before deploying to production, or when handling user data. Covers authentication, authorization, injection, data exposure, dependencies, and infrastructure.
Idioma del texto original: inglés
Use for ANY technical issue — test failures, bugs, unexpected behavior, performance problems, build failures, integration issues. Especially when under time pressure, when 'just one quick fix' seems obvious, or when previous fixes didn't work.
Idioma del texto original: inglés
Use during any implementation work — new features, bug fixes, refactors, behavior changes. Enforces the RED-GREEN-REFACTOR cycle. No production code without a failing test first.
Idioma del texto original: inglés
Use when a task could benefit from the skills library. Guides skill discovery, activation, composition, and effective application.
Idioma del texto original: inglés
Use when about to claim work is complete, fixed, passing, or done. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.
Idioma del texto original: inglés
Use when creating or updating documentation — READMEs, API docs, architecture docs, onboarding guides, or inline code documentation.
Idioma del texto original: inglés
Use when you need an absolutely thorough, no-shortcuts, multi-pass audit of the entire product. Covers build verification, route checking, data flow tracing, user flow testing, and edge case validation. Forces file-by-file verification with explicit tracking.…
Idioma del texto original: inglés
Use when integrating APIs from a product manager, designer, or spec document into an existing frontend. Covers full-surface mapping, modular API layer creation, systematic replacement of mocks/placeholders, and integration testing. Prevents partial…
Idioma del texto original: inglés
Use when a product looks 'done' but flows are broken, pages are placeholders, data is hardcoded, or the frontend and backend are not fully connected. Audits every route, every flow, every component for functional completeness vs visual completeness.
Idioma del texto original: inglés