mxa-stack
Establishes a project's stack at the start: what kind of work it is, which tool fills each purpose, where our work stops and the client's systems begin, and the thresholds every release must meet. It writes the record every other skill reads.
- Asks what kind of work this is first, a prototype, a pitch or production, because the answer changes every default.
- Detects an existing project's tooling rather than assuming it, and proposes defaults only where there is a gap.
- Agrees the baselines with the client: browsers and devices, the accessibility standard, the performance numbers, the licences.
- Says out loud where the experience layer ends and the systems layer begins, and whether that boundary is real yet.
- Writes the machine-readable manifest and the human-readable Stack Map, and files the audit moments as work items on a production engagement.
What is inside
Instructions. Nothing here runs on its own: the judgement is the skill.
- Evals
- 3
Works with
The outside tools and connectors this skill drives.
- Reads the project's code and config, then records what it found
A project that already has its own tool for this keeps it. The skill works with what is there rather than assuming what we would have chosen.