Make a useful process repeatable
A design review, release check or session recap often needs the same care every time. Save that procedure once, with a clear purpose and steps, instead of reconstructing it from a previous conversation.
Good workflows.
Ready for the next agent.
Stop rewriting the same review checklist in every chat. Keep the way you want work done alongside the knowledge your agents share.
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.
Skill summaries travel with project context. Full procedures load on request.
Choose what each project can use
Keep skills in your account library and assign them explicitly to the projects that need them. Each connected agent can discover that project's active skills. Your other projects and unassigned procedures stay separate.
Improve the procedure as you learn
Edit the central skill and preserve its earlier versions. Assigned projects receive the current active version on their next read. Archive a procedure when it no longer belongs in the working catalog.
Before you connect
Skills describe work; Memford does not execute a workflow engine or grant deployment permission. AI assessments remain assessments. Existing instructions and your authorization still apply.
Your next agent can start here.
Copy the brief. Connect the same project. Verify the first save.