cellm/skills/product-lens/SKILL.md
CELLM product thinking filter — every feature, skill, and API must work for external developers in any project, not just CELLM's own repository. Activates when designing plugin surfaces, Oracle APIs, MCP tools, or NPM-facing behavior.
npx skillsauth add murillodutt/cellm cellm/skills/product-lensInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
CELLM is a product installed via NPM in other people's projects. Before writing any feature, apply one filter:
"Would this work in a random Node.js project that installed CELLM?"
| Correct | Wrong |
|---------|-------|
| "CELLM users will..." | "We will use this to..." |
| Generic Node.js/Bun support | Only works in one specific internal repository |
| Skills for any project | Skills for CELLM development |
| Data in ~/.cellm/ | Data in repo directories |
data-ai
Prose override — temporarily disable quantization and respond in readable prose. Use when relational density matters, for safety-critical explanations, onboarding handoffs, or when token economy is not the priority.
development
Govern explicit weekly Super PRs or maintainer-requested PR merges. Evaluates a 10-criterion readiness checklist and performs governed merge only when a user-requested PR is READY. Never creates or keeps permanent PRs. Use when: 'pr-check', 'pr-merge', 'merge this PR safely', 'is PR ready', 'guard merge', or /sk-git delegates pr-merge.
data-ai
Operational surface for the compress-llm Layer-1 token I/O compressor. Enable, disable, switch mode, and inspect status without editing config files. Use when tuning compression pressure for the current session or project.
tools
Generate structured upstream feedback for the CELLM engineering team. Produces evidence-first Markdown at docs/evidence/<date>-cellm-feedback-*.md for bugs, anti-patterns, deprecation gaps, and harness surprises, with optional atom registration via knowledge_ops. Use when: 'feedback for CELLM', 'send to CELLM team', 'register this as atom', 'document this anti-pattern', 'report this bug upstream'. Trigger proactively on MCP schema/runtime mismatches, mechanical edit loops (>=3 sequential edits), short deprecation windows (<6 weeks), or reusable harness surprises. Do NOT trigger for routine feature work or project-local bugs.