creative-engineering-os
CLAUDE.md0 starsChanged 12 days agoMITView on GitHub
This repo is the reusable local toolkit, not the Pixelard website. Read SYSTEM.md, standards/STANDARD.md and the scoped task artifact. Use the relevant ceos specialist skill. Existing user/project instructions and host tool permissions take precedence. Keep dependencies pinned and scoped to tooling/templates/demo. Never open or print backups, auth files, provider config values or environment dumps. Client configs are outside the repo; change only owned additions after private backup and semantic preservation checks. One integration owner and explicit paths per specialist. Use…
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Keep dependencies pinned and scoped to tooling/templates/demo.
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md 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
Creative Engineering OS
This repo is the reusable local toolkit, not the Pixelard website. Read SYSTEM.md, standards/STANDARD.md and the scoped task artifact. Use the relevant ceos specialist skill. Existing user/project instructions and host tool permissions take precedence.
Keep dependencies pinned and scoped to tooling/templates/demo. Never open or print backups, auth files, provider config values or environment dumps. Client configs are outside the repo; change only owned additions after private backup and semantic preservation checks.
One integration owner and explicit paths per specialist. Use native/T3 child APIs supported by the host; never launch top-level conversations as substitutes. Tests exercise production previews, not only development. Inspect real images, report unverified checks honestly, preserve baseline history.
Local health: scripts/verify.sh; python3 tests/scripts.test.py; node --test tests/mirror.test.mjs. Template build/smoke/visual commands are in each README. Run GPU/performance jobs sequentially on a quiet machine.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- ceos-3d-asset-pipelineSkill
- ceos-art-directionSkill
- ceos-creative-codingSkill
- ceos-creative-directionSkill
- ceos-frontend-architectureSkill
- ceos-interaction-architectureSkill
- ceos-motion-directionSkill
- ceos-performance-engineeringSkill
- ceos-production-qualitySkill
- ceos-realtime-3dSkill
- ceos-shader-engineeringSkill
- ceos-start-hereSkill
- ceos-studio-workflowSkill
- ceos-visual-auditSkill
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.