agentleFS
Sign inStart free
wangge-aiwangge-ai/wangge-skills/skills/ecom-page-planner/SKILL.md

ecom-page-planner

Skill4 starsChanged 38 days agoMITView on GitHub

Use when planning ecommerce product-link positioning, visible selling-point

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write executable page tasks with copy limits, proof assets, layout intent, and acceptance criteria.

    line 27
  2. Very specific:

    Keep all business data and outputs under ./outputs/ecommerce\page-planning unless the user chooses another output directory.

    line 28
  3. Very specific:

    Use scripts/validate_output.py for category-link matrices.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ecommerce Page Planner

Plan the complete page strategy without blurring evidence and creative proposals.

Route the request

  • Visible competitor expression: read references/ecom-main-image-selling-point-analysis.md.
  • Buyer, pain point, benefit, and proof priority: read references/ecom-main-image-marketing-positioning.md.
  • Main-image sequence: read references/ecom-main-image-series-planner.md.
  • Detail-page screen plan: read references/ecom-detail-page-planner.md.
  • Multiple listing/link division: read references/ecom-category-link-positioning-matrix.md and references/category-output-contract.md.

Shared workflow

  1. Build an evidence pack from product facts, market data, visible competitor material, keyword data, and user feedback.
  2. Label every claim as fact, visible observation, inference, proposal, or missing evidence.
  3. Select only the requested planning layer; do not generate every artifact by default.
  4. Write executable page tasks with copy limits, proof assets, layout intent, and acceptance criteria.
  5. Keep all business data and outputs under ./outputs/ecommerce\page-planning unless the user chooses another output directory.

Use scripts/validate_output.py for category-link matrices. scripts/build_planning_artifact.py is a shared lightweight scaffold. Resolve the available Python runtime instead of assuming python is on PATH.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free