memex-implementation
Skill0 starsChanged 58 days agoMITView on GitHub
Implement or review Memex features when translating product specifications into the Memex Python package and CLI.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- adapt-to-projectSkill
- author-briefSkill
- author-delivery-briefSkill
- boy-scoutSkill
- bug-fixSkill
- capture-workSkill
- clean-commentsSkill
- clean-functionsSkill
- clean-generalSkill
- clean-namesSkill
- clean-testsSkill
- close-workSkill
- contract-acquisitionSkill
- init-projectSkill
- intake-intentSkill
- new-specSkill
- operational-safetySkill
- project-knowledgeSkill
- python-clean-codeSkill
- receive-briefSkill
- security-checklists-referenceSkill
- security-checklistsSkill
- work-intakeSkill
- work-loopSkill
- workspace-statusSkill
- definition-of-doneSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Keep the filesystem Markdown wiki as the source of truth.
- Distinctive: line 18
Before completing a feature, add or update behavior-focused tests and run Ruff, strict mypy, and pytest.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Memex implementation
Memex is the product, distribution, package namespace, CLI name, configuration
prefix, and local data directory. A source specification may retain an earlier
working title; translate its behavior into memex, do not expose that working
title as a public API.
Keep the filesystem Markdown wiki as the source of truth. SQLite is a rebuildable local search index only. Use the standard library for required features, validate all filesystem and archive inputs, and keep public APIs typed and keyword-only where optional arguments are involved.
Before completing a feature, add or update behavior-focused tests and run Ruff, strict mypy, and pytest. Avoid project skills, hooks, and agents unless they address a repeated workflow or the user explicitly requests them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.