johnoconnor0
UserClaude Code and Codex plugin marketplace for software delivery, business development and AI-assisted repository workflows.
Categories
Indexed Skills (22)
plan-completion-audit
Audit a project plan against the actual implementation — verifying code, types, security, and Supabase backend alignment.
skill-creator
Create, review, rebuild, validate, and package Claude Code skills or plugins. Use when the user asks to make a skill, improve an existing skill, convert a workflow into a skill, design a plugin, scaffold plugin agents/hooks/MCP/LSP integrations, or prepare an uploadable Claude extension.
skill-review
Security, safety, and quality review of Claude Code plugin marketplaces, plugins, and skills before install/approval. Use when the user asks to review, audit, vet, or approve a marketplace, plugin, or skill; check allowed-tools/permissions; scan for prompt injection, embedded secrets, or unsafe tool use; or produce a scored go/no-go report on Claude Code extensions.
service-outline
Generate a new Service Outline or update an existing one from John's modular 10-part service template, adapted to the service type (consulting, AI engineering, software development, web design, AI-driven PPC, branding). Interviews for context first; accepts an uploaded file, file path, or Notion/web URL as an update source. Use when the user asks to write, draft, update, or scaffold a service outline, service document, service brief, or service definition.
build-ui-prototype
Use when the user asks to build a UI prototype, clickable MVP, app shell, dashboard mock, product demo, or frontend proof-of-concept; to recreate a design from an image; to redesign an existing component; or to scaffold an app from requirements, UX flows, or an implementation plan.
create-data-model
Use to design the database schema after the PRD, technical design document, and architecture plan are agreed. Produces a durable schema file plus a generated JSON model, ERD, and migrations that later backend work reads back. Works on PostgreSQL, MySQL, SQLite, SQL Server and MongoDB. Use for entities, relationships, ownership, sensitive data, retention, indexes, access control, and migration risk.
create-design-system
Use when the user asks to plan, document, create, audit, or implement a design system, UI kit, component system, design tokens, typography, colours, spacing, accessibility rules, or reusable frontend component standards. Works for any stack, not only React - PHP, WordPress, Laravel, Vue and static HTML have their own adapters.
create-engineering-plan
Use to break approved product and architecture artifacts into sequenced, testable, low-risk implementation work.
create-prd
Use to produce a practical product requirements document with functional and non-functional requirements, user stories, acceptance criteria, assumptions, dependencies, success metrics, and release criteria.
create-system-map
Use to map actors, workflows, components, data flow, external systems, responsibility boundaries, failure points, security, and deployment shape.
create-technical-design-document
Use to turn product and system understanding into a technical design document - context, detailed design per component, data and API design, cross-cutting concerns, environments (preview/development/production), alternatives considered, and ADR candidates.
create-test-strategy
Use to define the automated and manual test plan for a product, feature, change, migration, release, or risk area, and to author the E2E specs. Can drive a real browser from the terminal via the Playwright CLI to verify behaviour before writing tests about it.
profile-product-system
Use at the start of product or repo work to understand the product, users, stack, integrations, constraints, and development maturity.
review-change
Use to review a branch, pull request, diff, or uncommitted change for correctness, architecture, security, tests, migrations, and maintainability.
run-engineering-council
Convene an independent multi-perspective engineering council before high-stakes or hard-to-reverse work — major architecture, a new plugin or subsystem, external integrations, risky migrations, security-sensitive or AI-system design, or build-vs-buy. Invoke proactively when a change is large, cross-cutting, or costly to undo, not only when explicitly asked; skip it for routine bug fixes and simple docs.
create-api-contract
Use to define REST, RPC, GraphQL, webhook, event, service, frontend-backend, or external integration contracts.
create-discovery-brief
Use to turn a product idea, problem, or vague initiative into a clear discovery brief with users, goals, risks, assumptions, and MVP boundary.
create-release-plan
Use to plan rollout, migration, feature flags, rollback, monitoring, support notes, changelog, and post-release validation.
create-ux-flow
Use to map user journeys, screens, states, interaction flows, accessibility considerations, and screen inventory for a product or feature.
map-product-lifecycle
Use to identify where a product or initiative sits in the engineering lifecycle and which artifacts are missing.
update-repo-hygiene
Use to inspect and intentionally update repository hygiene files such as .gitignore, .env.example, docs, changelog, and generated artifact reports.
implement-feature-safely
Use only after planning to guide implementation in small verified slices while respecting architecture, tests, repository conventions, and hygiene.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.