Start with work developers repeat
Design reviews, release checks and session recaps all benefit from a clear method. Free starter templates give you a beginning; your own skills can express the workflow that fits your projects.
Keep the process
that worked.
A useful review process should survive the chat where you first wrote it. Turn it into a reusable skill and make it available to the projects that need it.
A small catalog first. The full procedure only when the task needs it.
Assigned skill catalog
- Design reviewAssess, improve, check again
- Release checkVerify before shipping
- Agent handoffSave the next useful step
Load on request
Design review ยท full procedure
A repeatable review loop.
- Assess usability, design and accessibility.
- Fix the concrete issues.
- Review again, for up to three rounds.
Record evidence and unresolved issues.
The procedure stays in the library. The agent performs the work.
Separate rules from procedures
Use standards for the rules that should always accompany project context. Use skills for a particular task. Agents see the skill catalog first and request the full procedure when it becomes relevant.
Carry improvements into the next project
Update the procedure when you learn what was missing. Memford preserves its revisions, and assigned projects discover the current active version on their next read. Execution logs record what actually happened, separately from the recipe.
Before you connect
The library stores and serves skills; it does not run agents or deploy changes. External repository imports and automatic GitHub updates are not part of the current library.
Your next agent can start here.
Copy the brief. Connect the same project. Verify the first save.