feimacode8

name	ai-config
description	Manage AI assistant config files across tools. USE FOR: initializing AI configs for a new repo (AGENTS.md, CLAUDE.md, copilot-instructions.md, .cursorrules, GEMINI.md, etc.); adding a config for a newly adopted AI tool; detecting drift between multiple co-existing AI config files; updating preferences across all active configs; detecting when tooling changes (linter, framework, test runner) are not yet reflected in AI configs. Triggers on: 'set up AI configs', 'add Cursor config', 'my copilot instructions are out of date', 'sync my AI configs', 'check if my AI configs match the stack', 'onboard Claude Code'.
argument-hint	Optional: pass a mode to skip detection — init | add <tool> | check | edit | drift

AI Config Skill

Purpose

feimacode8

Error in user YAML: (<unknown>): mapping values are not allowed in this context at line 2 column 121

---
name: auto-test
description: Use when writing, reviewing, or diagnosing any automated test regardless of scope or framework. Triggers on: writing new tests, reviewing test quality, identifying test smells, naming tests, structuring test suites, or deciding which scope skill to apply.
---

Auto-Test: Universal Testing Principles

Overview

Core principles that apply to every automated test regardless of scope (unit, integration, e2e, contract, performance) or framework. Scope skills extend these; they do not replace them.

feimacode8

name	contract-test
description	Use when writing or reviewing contract tests that verify the agreement between a service consumer and a service provider, including consumer-driven contracts, schema validation, and provider verification.

Contract Test

Overview

A contract test verifies the agreement between a consumer and a provider — not their internal behaviour. The consumer defines what it expects from the provider; the provider verifies it can meet those expectations. Contract testing is a design discipline as much as a testing technique.

feimacode8

name	e2e-test
description	Use when writing or reviewing end-to-end tests that verify observable user-facing behaviour through the full stack with no mocks, covering browser flows, API journeys, or CLI interactions against a real or production-equivalent environment.

E2E Test

Overview

An end-to-end test verifies that a complete user-facing flow works correctly through the full stack. Nothing is mocked. The test interacts with the system the same way a real user or client would and asserts on observable outcomes.

feimacode8

Incident Triage

A skill for systematically triaging production incidents.

Purpose

When an incident occurs, this skill guides the AI to:

1. Gather initial context (error logs, recent changes, affected systems)
2. Identify the likely scope and severity
3. Propose immediate containment actions

feimacode8

name	integration-test
description	Use when writing or reviewing tests that verify a real integration boundary such as database queries, message queue interactions, external service calls, or inter-module wiring where real infrastructure is intentional.

Integration Test

Overview

An integration test verifies that two or more components work correctly when wired together through a real boundary — a database, queue, HTTP client, or file system. The use of real infrastructure is intentional; that is what distinguishes it from a unit test.

feimacode8

name	performance-test
description	Use when writing or reviewing performance tests that measure latency, throughput, resource utilisation, or scalability under load, and when asserting results against SLO thresholds as a pass/fail gate.

Performance Test

Overview

A performance test measures non-functional properties — latency, throughput, concurrency capacity, resource consumption — under a defined load profile. Results are statistical; pass/fail is determined by comparison against an explicit SLO baseline, not exact values.

feimacode8

name	repo-init
description	Interactive repo setup wizard. Use when: initializing a new repository, setting up project conventions, configuring dev tooling, choosing tech stack, setting up CI/CD, configuring AI tools. Guides user through structured questions covering repo structure (monorepo/polyrepo), tech stack (language, database, API, frontend, testing), AI tools (agents, methodology), and CI/CD (pipelines, IaC). Produces a reviewed summary and generates config files.
argument-hint	Optional: pass a specific section to jump to (repo-structure, tech-stack, ai-tools, ci-cd)

Repo Init Wizard

Purpose

feimacode8

name	unit-test
description	Use when writing or reviewing unit tests that test a single function, class, or module in isolation with all external dependencies replaced by test doubles.

Unit Test

Overview

A unit test verifies the behaviour of one unit (function, class, or module) in complete isolation. Every dependency that crosses an architectural boundary is replaced by a test double. Speed and determinism are non-negotiable.

feimacode8

Status Update

A prompt template for incident status updates.

Purpose

Generate clear, concise status updates for stakeholders during an incident.

Template