mean.md Software-to-Software Starter Kit
Use this kit to define the first workflow, the instruction layer, the tool access and the review checks for a small software-to-software system.
What the starter kit includes
Project instruction file
A short AGENTS.md outline for goals, files, tools, approval rules and QA.
Design file
A design.md outline for colors, typography, layout behavior, components and mobile fit.
Workflow map
A one-page map for the task, trigger, tools, files, review step and owner.
MCP readiness checklist
A checklist for deciding whether the workflow needs MCP, an API, a manual step or a simpler file-based path.
Publishing QA checklist
A review list for source copy, HTML, metadata, links, forms, legal pages, mobile rendering and WordPress readiness.
Use-case path
A way to choose the first workflow across coding, marketing, operations, research, content and personal systems.
First workflow outline
- Name the repeated task.
- List the files, apps and accounts involved.
- Write the instruction the agent should follow.
- Decide which actions require review.
- Define the test that proves the output is usable.
- Record what changed after the first run.
Starter AGENTS.md outline
# Project Instructions
## Goal
Describe what the project should help the builder do.
## Files
List the files that own copy, design, data, pages and QA.
## Rules
State the writing, design, privacy and approval rules.
## Checks
List the checks that must pass before work is complete.Read the agent instruction guide for the file layer, the MCP guide for the connection layer and the use-case page for choosing the first workflow.