MCP server "love-claude-code-ui" as configured in ArtemioPadilla/love-claude-code. Launched with ./mcp-server/dist/index.js. Needs 3 environment variables to run.
★not rated 5 6mo agoA
tokens not measured
originalMIT
MCP server "love-claude-code-providers" as configured in ArtemioPadilla/love-claude-code. Runs ./backend/dist/mcp/provider-server.js with node. Needs 1 environment variable to run.
★not rated 5 6mo agoA
tokens not measured
originalMIT
QA Engineer and Security Auditor agent for code review, security auditing, testing verification, compliance checking, dead code detection, and quality gates. MUST BE USED for any review, audit, quality check, or security assessment. Use PROACTIVELY after any code changes or before releases.
Developer and Software Architect agent for architecture decisions, full-stack implementation, code writing, testing, infrastructure, CI/CD, and technical documentation. MUST BE USED for any coding, implementation, architecture, refactoring, or technical task. Use PROACTIVELY when the user needs code written, bugs…
Product Manager agent for product strategy, feature specifications, user stories, business logic, prioritization, and roadmap management. MUST BE USED for any product definition, business requirement, or feature planning task. Use PROACTIVELY when the user discusses features, requirements, business logic, or product…
Post-implementation business assessment by Prometeo (PM). Verifies success metrics achievement, scope compliance, acceptance criteria business interpretation, risk materialization, and product decision closure. Outputs structured report with verdict and confidence score.
Analyzes checklist effectiveness by tracking hit rates, identifying stale items, and finding coverage gaps. Generates evolution suggestions following Boorman's principles. Use periodically to keep checklists field-tested and relevant.
Scans the codebase for dead code, tech debt, outdated dependencies, and code quality issues. Use periodically or before releases to maintain code hygiene.
Creates a complete product feature specification. Use when defining new features, writing user stories, or planning product work. Generates structured specs in docs/specs/.
Generates test cases for a module or function following FIRST principles and Arrange-Act-Assert pattern. Detects test framework from project config. Use to bootstrap test coverage for existing code or as the Red phase of TDD.
Create and manage git worktrees for isolated feature work. Use when starting implementation that should not touch the main workspace, or for parallel development. Handles creation, baseline verification, and cleanup.
Implements a feature from its specification. Reads the spec, designs architecture, writes code, tests, and documentation. Use after a feature spec has been approved.
Handle code review feedback with technical rigor — verify before implementing, push back when reviewer is wrong, no performative agreement. Use when receiving feedback from Centinela, external reviewers, or PR comments.
Rebuilds the codebase knowledge index at docs/codebase-index.json. Scans all source files for module structure, exports, dependencies, and tech debt hotspots. Shared across all three agents.
Deep security audit of code, dependencies, and infrastructure. Checks OWASP Top 10, authentication, authorization, data protection, and dependency vulnerabilities. Use before releases or after significant changes.
Inline verification for any written artifact — specs, plans, reviews, docs. Runs 4 checks in under 60 seconds. Use on demand outside the triforce flow, or rely on TIME OUT checklists during normal agent operations.
Runs controlled failure simulations to verify that agents correctly invoke their Non-Normal (emergency) checklists. Available scenarios: ambiguous-spec, failing-tests, security-finding. All outputs are labeled SIMULATION MODE and written to docs/training/.
Execute an implementation plan by dispatching fresh subagents per task with two-stage review (spec compliance, then code quality). Use for ad-hoc plan execution outside the full triforce ceremony.
4-phase root cause debugging process. Use when encountering any bug, test failure, or unexpected behavior BEFORE proposing fixes. Prevents guess-and-check thrashing. Includes root-cause tracing, defense-in-depth, and architecture questioning.
★not rated 3 6mo agoA50 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: