adapt-framework

Adapts a KATA test boilerplate's auth, schemas, fixtures, CI, and MCP config to a discovered target project.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/ahuaracab/test-genesis --skill adapt-framework-ahuaracab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adapt-framework
Source: https://github.com/ahuaracab/test-genesis/tree/main/.agents/skills/adapt-framework
Command: npx skills add https://github.com/ahuaracab/test-genesis --skill adapt-framework-ahuaracab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After reverse-engineering a project, teams still face the tedious, error-prone work of rewiring a generic test boilerplate — auth flows, OpenAPI types, fixtures, CI workflows, and MCP registries — to match the real target stack. This Skill automates that adaptation with a strict approval-gated, idempotent workflow. ## Core Features & Use Cases - Gated Phase 0-9 Workflow: Runs analysis and planning with no writes, produces an approval-pending plan, then executes identity, OpenAPI, auth, entity, CI, and MCP wiring only after explicit user approval. - Idempotent Genericness Scan: Detects which boilerplate artifacts (example components, hotel/booking data, PROJ-/UPEX- keys) are still generic versus already adapted, so re-runs only complete remaining work. - Auth and API Wiring: Adapts AuthApi, LoginPage, Playwright auth setups, and the api-login script to the target's token, cookie, or hybrid auth contract, including OpenAPI sync and type facades. - Use Case: After running project-discovery on a new repo, invoke this Skill to replace all example artifacts, wire real staging credentials and endpoints, reconcile GitHub workflows and MCP configs, and finish with a validated smoke test. ## Quick Start Ask the agent to adapt the test framework to this project using the context generated by project-discovery, then approve the generated plan before any files are written.

Frequently Asked Questions about adapt-framework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I adapt a test automation boilerplate to my own project?

Run project-discovery first to populate the .context directory, then invoke this Skill. It analyzes your stack, writes an approval-gated plan, and only after approval rewires auth, schemas, fixtures, CI, and MCP configuration to your target project.

How do I wire Playwright authentication for token-based APIs?

The Skill adapts AuthApi, LoginPage, and the api-auth and ui-auth setup files to your login endpoint, payload fields, and token response shape. It supports token, cookie, and hybrid CSRF strategies, verified by running the setup projects and a curl smoke check.

Can I re-run the framework adaptation if it was partially completed?

Yes, the workflow is idempotent. A genericness scan detects which subsystems still contain example artifacts versus those already adapted, and re-runs plan and execute only the remaining items.

What prerequisites are required before adapting the test framework?

The .context directory must be populated by project-discovery, including architecture, infrastructure, business data map, and a resolvable API contract source such as an OpenAPI spec. Missing prerequisites block execution with exact remediation commands.

Does the adaptation modify my target application repository?

No, it modifies only the boilerplate repository containing the test framework. The target repository is treated as read-only throughout all phases of the workflow.

When should I not use this framework adaptation workflow?

Do not use it for writing feature tests, running regression suites, or regenerating project context. Those belong to the test-automation, regression-testing, and project-discovery skills respectively.