How does it handle data storage recommendations?

It encourages using standardized global locations like the user home directory instead of local repo directories to ensure data persistence across different projects.

Does this skill support specific runtimes?

Yes, it promotes generic support for standard environments like Node.js and Bun rather than relying on specific internal repository structures.

What is the primary goal of the Product Lens skill?

The primary goal is to ensure that any feature or tool you build is project-agnostic and ready for external use by developers in any Node.js project.

When does this skill activate?

It activates automatically when Claude is designing plugin surfaces, Oracle APIs, MCP tools, or any NPM-facing behavior.

Is Product Lens a user-invocable command?

No, it is a background filter that guides Claude's reasoning and code generation to maintain high standards for product portability.

Product Lens

Name: Product Lens
Author: murillodutt

bymurillodutt

0•

Developer Tools

Enforces product-centric design principles to ensure tools and APIs are universally compatible and ready for external distribution.

Product Lens is a specialized capability for Claude Code that acts as a quality filter during the development process, prioritizing external portability and developer experience. It ensures that any feature, skill, or API built within the CELLM ecosystem is designed for the end-user rather than internal convenience, preventing hardcoded paths and repo-specific assumptions. By activating during the design of plugin surfaces and NPM-facing behaviors, it helps developers build robust, project-agnostic tools that function seamlessly across any Node.js environment.

Key Features

01Prevents hardcoded internal paths and repo-specific logic

02Validates external compatibility for NPM-distributed packages

03Standardizes storage patterns using global user directories

04Guides the design of universal plugin surfaces and Oracle APIs

050 GitHub stars

06Enforces dynamic project structure discovery and configuration

Use Cases

01Designing a new MCP tool intended for public NPM distribution

02Refactoring internal utilities into reusable open-source plugins

03Auditing code to ensure it works in a clean, third-party Node.js environment

Key Features

01Prevents hardcoded internal paths and repo-specific logic

02Validates external compatibility for NPM-distributed packages

03Standardizes storage patterns using global user directories

04Guides the design of universal plugin surfaces and Oracle APIs

050 GitHub stars

06Enforces dynamic project structure discovery and configuration

Use Cases

01Designing a new MCP tool intended for public NPM distribution

02Refactoring internal utilities into reusable open-source plugins

03Auditing code to ensure it works in a clean, third-party Node.js environment