Choose the tools.
Skip the hype.

When it fits. Use for a specific investigation of software you are authorized to inspect. Target support and native-analysis providers affect setup.

“Anything” is a project slogan, not a promise of universal analysis or perfect reconstruction.

Illustrative use. Identify how an approved legacy application implements one feature; ask for evidence and unresolved questions.

When it fits. Useful when an agent overbuilds or adds needless abstractions. Check installation instructions for your specific host.

The shortest implementation still has to meet correctness, security and maintenance requirements.

Illustrative use. Ask for the smallest change that meets the acceptance criteria, with explicit trade-offs.

When it fits. Try for a new landing page or a substantial redesign. Its README names Claude Code, Cursor and Codex.

Distinctive styling does not establish usability, accessibility or brand fit. Validate the finished interface.

Illustrative use. Create a property-project page from approved brand assets and content; test the mobile enquiry flow.

When it fits. Useful for editing a completed draft. Review facts, quotations and intended tone after rewriting.

It does not make content factual, prove human authorship or guarantee any detector outcome.

Illustrative use. Edit an investor introduction for specificity and plain language while retaining every factual claim.

When it fits. Assess hosting, model configuration, connectors, access controls and ongoing operations before adopting it.

The blueprint links to the wrong project. Use onyx-dot-app/onyx; self-hosting alone does not prove that all data stays local.

Illustrative use. Pilot with a small approved document collection and test whether users see only the material they may access.

When it fits. Useful for improving an existing UI. Follow the current setup instructions for the selected coding tool.

A design audit still needs real keyboard, responsive and user-flow checks. Command availability can change.

Illustrative use. Audit a sales planner for hierarchy, field clarity and mobile usability, then fix the highest-impact issues.

When it fits. Use to guide a design system or a new interface. Check the current host support and runtime requirements.

Style guidance is not a substitute for user research or testing. Avoid conflicting instructions from several design skills.

Illustrative use. Specify a mobile-first dashboard with consistent typography, spacing, form states and accessible contrast.

When it fits. Useful for discovering recent themes. Check required services, API credentials and usage charges in the README.

Online discussion is not a representative market sample or verified sales evidence. Recency alone does not establish accuracy.

Illustrative use. Find recent objections in a market, then validate them against customer interviews and CRM records.

When it fits. Use when structured collection is needed. Expect runtime setup and site-specific extraction validation.

Extraction can fail when pages change. Respect access restrictions, permitted use and data minimization.

Illustrative use. Collect permitted public listing fields, preserve source URLs and timestamps, and check a sample against the pages.

When it fits. Useful for architecture, process and explanatory diagrams. Choose a representation that matches the information.

Interactivity is not necessary for every diagram. Visual polish does not validate the underlying relationships.

Illustrative use. Explain the lead-to-sale process with explicit stages, decision points and ownership.

When it fits. Use when studying an approved reference. Review the host and browser setup described by the project.

Design analysis does not grant rights to copy assets or branding; translate the principles into an original implementation.

Illustrative use. Study a reference’s spacing and hierarchy, then apply suitable principles to an original ImageFirm design.