Manufacturing
Roster, test boundaries and repo map are in ~/repository/enviaflores/CLAUDE.md (always loaded inside enviaflores repos). This skill holds the playbooks. Read only the file the task needs.
| Task | Read |
|---|---|
| Who is who, modules per dev, QA rotation, unknown board logins | team.md |
| Create or fill an issue (Epic / Story / Task / Bug), project 59 fields | issues.md + templates/ + scripts/new-issue.sh |
| Find how a legacy screen works (repo, controller, tables, rules) | legacy-research.md |
| Telemetry: errors, latency, alerts, dashboards, ECS/ALB | grafana.md |
| What is each dev doing, who has no task, my pending work | scripts/dev-status.sh (see team.md) |
| Notion databases, @mentions, QA User field | notion.md |
| Obsidian notes (trackers, checklists, runbooks) | obsidian.md |
| Review or test a teammate's PR, work a QA bug | review-and-qa.md |
| Commit/PR, core-pkg release + host bump, permissions for new screens | releases.md |
| CBQ brokers and daemons in the dev container (redis, sqs/elasticmq, ordered event commands), never prod | cbq.md |
| Workshop print servers: workshop-daemon code and server layout, labeler API, how the app finds the server, deploy, new Zebra queue, "can't print" diagnosis | print-server.md + scripts/labeler-test.sh |
| ZPL label templates: Labelary previews, measuring, dpi scaling, QR and font sizes | labels.md |
Always
- GitHub scripts (
dev-status.sh,new-issue.sh,bump.sh) run as the work accountEdgardoAcostaEFwhateverghaccount is active: prefix each call withGH_TOKEN=$(gh auth token --user EdgardoAcostaEF). The scripts know nothing about accounts. - Spanish for issue bodies, Notion and team-facing text.
- No code comments by default, config files included. Add one only when the code is not self-explanatory or encodes a business rule, then one line, always in English. No block headers, no "why we chose this" (that goes in the commit/PR).
- Preview anything outward (issue, Notion row, Grafana rule) and wait for an explicit yes. Never post GitHub comments; status notes go to Obsidian.
- Legacy is the business-logic source of truth. Parity first; deviate only for real defects (wrong data, lost rows, security) and list them.
- Diagrams: in a presentation or deck, build them with the
archifyskill (export the diagram only, no cards or index, into the slide). In Obsidian notes, use mermaid. - Keep this skill current: when I learn a durable fact about the team, the board, legacy or telemetry, edit the matching file in the skills repo checkout (
~/repository/personal/claude-skills/plugins/ef-manufacturing/skills/manufacturing/), never the installed plugin copy, then push and runclaude plugin update ef-manufacturing@edgardo-skills. Do not write a new memory for it.