Claude Skills by JarodFroneman

Run evidence-bound, read-only JStack code audits across correctness, security, architecture, maintainability, performance, supply chain, tests, data integrity, compatibility, and operations. Use when the user invokes the jstack-audit skill or command, requests a repository audit or release go/no-go review, asks to challenge existing findings, or wants the JStack audit mastery track.

Run JStack's enterprise Chief Security Officer audit across application, API, frontend exposure, authorization, proprietary logic, AI prompt injection, infrastructure, supply chain, browser controls, abuse detection, and incident readiness. Use when the user invokes jstack-cso, requests a CSO or application-security audit, asks what the browser exposes, or wants a security posture report without remediation.

Evidence-driven enterprise engineering and mastery workflow for JStack projects. Use when the user invokes /j-stack-dev, /jstack-subagents, or /jstack-full-team, or asks for JStack planning, implementation, review, QA, security, release readiness, project handoff, or deliberate engineering training.

Build private, digest-bound Product Interface reference bundles from user-provided screenshots, Figma exports, or explicitly approved URLs. Use when the user invokes /jstack-evidence-builder or asks JStack to turn visual references into structured design evidence or an isolated HTML prototype before implementation.

Run bounded JStack goal loops or durable multi-phase programs until current acceptance evidence succeeds or an auditable stop or wait state is reached. Use when the user invokes /jstack-loop, asks JStack to keep working toward a goal, requests a long-running or monolithic project with human checkpoints, or combines loop engineering with single-lead, specialist-team, or full-team JStack delivery.

Design, implement, modify, or review user-facing graphical interfaces with JStack's Product Interface System. Use automatically for frontend and UI work involving screens, routes, components, forms, dashboards, mobile or native views, webviews, desktop windows, or canvas, editor, and timeline experiences, including visual, responsive, interaction, accessibility, and visual-QA changes. Do not use for backend-only, API-only, infrastructure, data, CLI or TUI, or documentation-only work with no g...

Single Lead Engineer JStack workflow. Use when the user invokes /j-stack-dev or asks for the standard JStack development workflow without subagents.

Design, implement, modify, or review user-facing graphical interfaces with JStack's Product Interface System. Use automatically for frontend and UI work involving screens, routes, components, forms, dashboards, mobile or native views, webviews, desktop windows, or canvas, editor, and timeline experiences, including visual, responsive, interaction, accessibility, and visual-QA changes. Do not use for backend-only, API-only, infrastructure, data, CLI or TUI, or documentation-only work with no g...

Run evidence-bound, read-only JStack code audits across correctness, security, architecture, maintainability, performance, supply chain, tests, data integrity, compatibility, and operations. Use when the user invokes the jstack-audit skill or command, requests a repository audit or release go/no-go review, asks to challenge existing findings, or wants the JStack audit mastery track.

Run JStack's enterprise Chief Security Officer audit across application, API, frontend exposure, authorization, proprietary logic, AI prompt injection, infrastructure, supply chain, browser controls, abuse detection, and incident readiness. Use when the user invokes jstack-cso, requests a CSO or application-security audit, asks what the browser exposes, or wants a security posture report without remediation.

Build private, digest-bound Product Interface reference bundles from user-provided screenshots, Figma exports, or explicitly approved URLs. Use when the user invokes /jstack-evidence-builder or asks JStack to turn visual references into structured design evidence or an isolated HTML prototype before implementation.

Dynamically composed JStack workflow with complete material engineering coverage. Use when the user invokes /jstack-full-team or explicitly asks to deploy the full JStack team.

Run bounded JStack goal loops or durable multi-phase programs until current acceptance evidence succeeds or an auditable stop or wait state is reached. Use when the user invokes /jstack-loop, asks JStack to keep working toward a goal, requests a long-running or monolithic project with human checkpoints, or combines loop engineering with single-lead, specialist-team, or full-team JStack delivery.

JStack specialist-team workflow. Use when the user invokes /jstack-subagents or explicitly asks to deploy the right subagent team, normally two or three specialists.

Run evidence-bound, read-only JStack code audits across correctness, security, architecture, maintainability, performance, supply chain, tests, data integrity, compatibility, and operations. Use when the user invokes the jstack-audit skill or command, requests a repository audit or release go/no-go review, asks to challenge existing findings, or wants the JStack audit mastery track.

Run JStack's enterprise Chief Security Officer audit across application, API, frontend exposure, authorization, proprietary logic, AI prompt injection, infrastructure, supply chain, browser controls, abuse detection, and incident readiness. Use when the user invokes jstack-cso, requests a CSO or application-security audit, asks what the browser exposes, or wants a security posture report without remediation.

Evidence-driven enterprise engineering and mastery workflow for JStack projects. Use when the user invokes /j-stack-dev, /jstack-subagents, or /jstack-full-team, or asks for JStack planning, implementation, review, QA, security, release readiness, project handoff, or deliberate engineering training.

Build private, digest-bound Product Interface reference bundles from user-provided screenshots, Figma exports, or explicitly approved URLs. Use when the user invokes /jstack-evidence-builder or asks JStack to turn visual references into structured design evidence or an isolated HTML prototype before implementation.

Run bounded JStack goal loops or durable multi-phase programs until current acceptance evidence succeeds or an auditable stop or wait state is reached. Use when the user invokes /jstack-loop, asks JStack to keep working toward a goal, requests a long-running or monolithic project with human checkpoints, or combines loop engineering with single-lead, specialist-team, or full-team JStack delivery.

Design, implement, modify, or review user-facing graphical interfaces with JStack's Product Interface System. Use automatically for frontend and UI work involving screens, routes, components, forms, dashboards, mobile or native views, webviews, desktop windows, or canvas, editor, and timeline experiences, including visual, responsive, interaction, accessibility, and visual-QA changes. Do not use for backend-only, API-only, infrastructure, data, CLI or TUI, or documentation-only work with no g...