claude

verid

Self-contained verid BA, onboard, design, planning, TDD, debugging and review skills with architect, planner, tester, coder, QA, reviewer and security agents

1 on GitHubby Anh Tranv1.2.0MITupdated 6 days ago
/

Plugin verid from marketplace verid in anhtranhai835/aeriq. Commands read from the repo's manifest — 5 days ago.

What it installs

Skills (32)

  • verid-ba

    Use when a verid project needs requirements research, scope clarification, EARS specification (.verid/spec.md), or modular BA dossiers.

  • verid-build

    Use when an approved verid module is ready for TDD implementation (RAW -> COOKING -> PLATED) and verification with verid taste.

  • verid-debugging

    Use when a test fails unexpectedly, a bug is reported, or an implementation is stuck during a verid cycle.

  • verid-design

    Use when a verid project has agreed research and spec and needs architecture decisions, reuse inventory, and .verid/design.md.

  • verid-onboard

    Use when onboarding to a verid workspace, checking setup health, or reporting current module status and next step without modifying files.

  • verid-plan

    Use when a verid design is agreed and needs delivery modules and testable acceptance criteria in .verid/plan.md (classic, modular, or kanban).

  • verid-review

    Use when all ACs of an ordered verid module pass and need an independent subagent review before verid serve.

  • verid-router

    Use when a verid task touches a specific domain (UI/UX, React, Frontend, Backend, Databases, DevOps, Mobile, Web-Testing, Edge-Cases, Security-Scan, Docs-Seeker) to load only the needed reference file.

  • ba

    Use when verid requirements or scope need research, clarification or a spec.

  • backend-development

    Use for API, authentication, service, and backend architecture work.

  • context-engineering

    Use for selective document reading, focused agent handoffs, context loss or token waste in verid workflows.

  • databases

    Use for schema design, queries, indexes, migrations, and data integrity.

  • debugging

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

  • design

    Use when a verid project needs an agreed design before planning modules.

  • devops

    Use for CI, containers, cloud infrastructure, and deployment design.

  • docs-seeker

    Use to find current library or framework documentation for an implementation decision.

  • edge-cases

    Use when an AC has input, state, permission or timing boundaries.

  • frontend-development

    Use for React or TypeScript UI implementation and component structure.

  • mcp-builder

    Use when building a Model Context Protocol server or tool integration.

  • mobile-development

    Use for iOS, Android, React Native, or Flutter development.

  • modules

    Use when workflow is modular to prepare module dossiers from repo templates and carry their contracts through verid order, TDD, review and release.

  • onboard

    Use when a developer is new to a verid project or asks whether their workspace is set up and where the project stands.

  • plan

    Use when a verid design is agreed and needs modules with testable acceptance criteria.

  • predict

    Use before a major or risky verid design change to examine architecture, security, performance, user experience, and hidden assumptions.

  • problem-solving

    Use when a verid task is stuck because of growing complexity, repeated failed approaches, hidden assumptions, or uncertain scale.

  • react-best-practices

    Use for React and Next.js performance reviews and implementation.

  • review

    Use when a verid module is ready for review, a signed auto plan needs review, or the product is ready for handoff.

  • security-scan

    Use for an authorized codebase scan for secrets, vulnerable dependencies, and risky code paths.

  • security

    Use when a verid module needs a security review before closure, alone or as the security part of a combined review.

  • tdd

    Use when writing or changing verid tests and production code.

  • ui-ux-pro-max

    Use for UI layout, design systems, accessibility, and interaction design.

  • web-testing

    Use for browser, accessibility, visual, load, and integration test design.

Subagents (14)

  • architect

    Use when agreed verid research needs an architecture proposal or an approved design draft.

  • brainstormer

    Use when a verid feature needs a focused comparison of possible approaches before design approval.

  • code-simplifier

    Use after a passing verid cycle when recently changed code may be simpler without changing behavior.

  • coder

    Use when a verid AC has a recorded failing test or an open stub step.

  • debugger

    Use when a verid test, build, or runtime failure needs a second read-only root-cause investigation.

  • docs-manager

    Use when documentation needs an accuracy and consistency review against verid's code and decisions.

  • planner

    Use when a verid design needs proposed module boundaries or an approved plan draft.

  • project-manager

    Use when the developer needs a factual progress report across verid modules.

  • qa

    Use when a verid (e2e) acceptance criterion needs a failing test of the real product.

  • reviewer

    Use when a verid module, whole product or signed auto plan needs an independent review.

  • security

    Use when a verid module has passed correctness review and needs its security review.

  • technical-researcher

    Use when a verid design or implementation needs current technical evidence outside the repository.

  • tester

    Use when one verid acceptance criterion needs its failing test before implementation.

  • ui-ux-designer

    Use when a verid module changes a screen and needs a focused UI and accessibility critique.

View source on GitHub

Maintain verid?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted