TSH Product Engineering

Plugin tsh-product-engineering from marketplace tsh-agentic-collections in TheSoftwareHouse/agentic-collections. Commands read from the repo's manifest — today.

Skills (9)

• auditing-application-security

  Audits an application's code and dependencies for security across a whole service or a named surface — not a single change — and triages scanner and advisory output into a severity-ranked report. Runs only the security scanners the project already has, never installs them, and applies an optional st

• capturing-ui-evidence

  The mechanical capture contract for UI verification: drives the playwright-cli against the pinned dev server URL to collect actual.png, computed-styles.json and a11y-snapshot.yml into the iteration artifact directory. Works with no design reference at all; when — and only when — the caller supplies

• creating-implementation-plans

  Writes TSH's implementation plan as a committed file at specifications/<task-id>/<task-name>.plan.md: phased tasks that each name their files and a verifiable Definition of Done, technical context persisted for implementers, explicit parallel groups. Use when a plan, spec, or task breakdown is asked

• debugging-code

  Finds and fixes the root cause of a bug: pins the symptom, reproduces it, secures a failing test — existing, corrected or new — narrows to the cause with evidence rather than plausibility, measures how far the fix reaches before applying it minimally, and keeps the test as a regression guard. Use wh

• discovering-technical-context

  Establishes which conventions a change must follow before it is written, in priority order: the plan's persisted technical context, then project instructions (CLAUDE.md, .claude/rules, decision records), then existing codebase patterns, then external documentation. Use to answer 'how does this proje

• orchestrating-feature-implementation

  Implements a feature, ticket, or plan end to end from the main conversation: confirms a plan file exists, delegates each task to implementer subagents — in parallel where the plan allows — gates on their reports, then closes with the plan's final verification phase: code review and functional verifi

• reviewing-code

  TSH's pre-merge review of a delivered change set — a pasted diff, a task, or a PR: reads the plan and requirements first, compares the implementation against what was agreed, judges test coverage per layer, runs the project's tests, linters and build when they are available, then checks high-risk an

• reviewing-ui

  Runs one UI verification pass against Figma: delegates fresh Playwright-CLI capture of the running app to ui-capture-worker, then the design comparison to ui-reviewer, and returns PASS, FAIL, or VERIFICATION NOT RUN with a complete difference table. Read-only — it never fixes code. Use when asked to

• verifying-ui

  The standard for judging implemented UI against its Figma design: EXPECTED comes only from the Figma MCP, ACTUAL only from live Playwright-CLI capture artifacts, compared across structure, layout, dimensions, visual and components under strict tolerances, ending in PASS, FAIL, or VERIFICATION NOT RU

Subagents (7)

• code-reviewer

  Reviews a delivered change set against its plan and requirements — executes tests, linters, and build, judges coverage, checks security and high-risk anti-patterns — and returns a structured findings report. Use after implementation tasks complete, before merge.

• feature-verifier

  Executes a plan's verification document against the running application — committed E2E suites, browser walkthroughs with examined screenshots, real API calls, database and log checks — and returns per-scenario evidence. Use in a plan's final verification phase, in parallel with code review.

• security-auditor

  Audits an application's code and dependencies for security across a whole service or a named surface — maps the attack surface, runs the security scanners the project already has, applies the universal baseline plus any named standard, triages advisories by reachability, and returns a severity-ranke

• software-engineer

  Implements delegated implementation-plan tasks — application code, tests, and configuration — exactly as specified, and verifies each with the plan's own commands. Use to execute one or more tasks from a *.plan.md, including several agents in parallel across independent tasks.

• ui-capture-worker

  Collects UI verification evidence from a running app with the Playwright CLI — full-page screenshot, computed styles, accessibility snapshot — into the iteration artifact directory, and exports the shared Figma reference image when given a Figma URL. Use during UI verification, always before ui-revi

• ui-engineer

  Implements UI components and frontend changes from a design reference, fetching the Figma design before writing code and verifying the rendered result in a browser against it. Use for plan tasks that change rendered UI, especially Figma-backed screens and components.

• ui-reviewer

  Judges implemented UI against its Figma design from live capture artifacts — multimodal screenshot comparison plus computed styles and accessibility snapshot — and returns PASS, FAIL, or VERIFICATION NOT RUN with a complete difference table and recommended fixes. Use after ui-capture-worker has prod

Similar plugins