详情页结构
/详情页结构
Write or restructure an e-commerce product detail page screen by screen (first screen, selling points, usage scenes, specifications, comparisons, objections, after-sales), with the copy and the image brief for each screen. Use when a product detail page is written from product information, when an existing page is rewritten, or when the designer needs a page plan.
- Author
- pm-shawn ↗
- Repository
- abu-cowork ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Write or restructure an e-commerce product detail page screen by screen (first screen, selling points, usage scenes, specifications, comparisons, objections, after-sales), with the copy and the image brief for each screen. Use when a product detail page is written from product information, when an existing page is rewritten, or when the designer needs a page plan.
Arguments
/详情页结构 [商品参数、卖点、评价或现有详情页]
Original author description
Write or restructure an e-commerce product detail page screen by screen (first screen, selling points, usage scenes, specifications, comparisons, objections, after-sales), with the copy and the image brief for each screen. Use when a product detail page is written from product information, when an existing page is rewritten, or when the designer needs a page plan.
How it works
- Screens
- Platform notes
- Output
SKILL.md preview
--- name: 详情页结构 description: Write or restructure an e-commerce product detail page screen by screen (first screen, selling points, usage scenes, specifications, comparisons, objections, after-sales), with the copy and the image brief for each screen. Use when a product detail page is written from product information, when an existing page is rewritten, or when the designer needs a page plan. display-description: zh-CN: 按一屏一屏的结构写商品详情页,附每屏的配图说明 en-US: Write a product detail page screen by screen, with an image brief for each screen trigger: The user asks for a product detail page, a rewrite of one, or a detail-page plan for the designer. argument-hint: "[商品参数、卖点、评价或现有详情页]" --- # Detail page structure Build the page from the product information the user supplies. Every factual claim (material, size, capacity, effect, certification, warranty, shipping) must come from that information; where something is missing, write a placeholder such as `[质保期限]` and list all placeholders at the end. Do not invent test data, sales numbers, awards or endorsements. Customers read detail pages on a phone and stop early. Put what decides the purchase first, keep each screen to one idea, and keep text short enough to read on an image. ## Screens 1. **First screen**: product name, the single strongest benefit in one line, and the one fact that proves it. This screen must make the customer want to keep scrolling. 2. **Core selling points** (three to five): each one as a short heading (the benefit), one or two lines of explanation (the supporting fact), and the image that proves it. Order them by what the user's reviews, questions or competitor gaps show customers care about most. 3. **Usage scenes**: who uses it, where and how. Show the product in real use. 4. **Details and craftsmanship**: close-ups that support quality claims made above. 5. **Specifications**: a clear table of the user's specifications; add a size guide, compatibility list or what is in the box when relevant. 6. **Comparison** (optional): versus the customer's alternative or the previous version, using only facts the user supplied. Never name or disparage a competitor brand. 7. **Answers to objections**: the three to five questions or worries that stop people buying, taken from the user's chat logs, Q&A or negative reviews when available, each with a short answer. 8. **After-sales and trust**: shipping, returns, warranty and service exactly as the store's policy states. ## Platform notes Taobao/Tmall and JD pages are long image-led pages; Pinduoduo customers are price-sensitive, so put the value and the bundle contents early; Douyin and Xiaohongshu shoppers often arrive from content, so the first screens should match the video or note that brought them. Image width, length limits and text rules differ by platform and change; tell the user to confirm the current image guidelines. ## Output For each screen: purpose, headline, body copy, image brief (what to show, composition, text overlay). Then a compliance check of all copy for absolute and unverifiable claims with alternatives, and the list of placeholders still to fill.
Versions
The database has no other skills named 详情页结构.
Database snapshot: 13.11.2026 · package version 9c082f1dc160 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100detail-flow
Build, redesign, polish, or review product detail pages for products, AI tools, models, SaaS features, developer products, plugins, ecommerce listings, and technical showcases. Use when the user provides a product image, reference image, screenshot, product concept, or existing… - 100landing-page-copy
Write landing-page copy section by section - hero, social proof, features-as-benefits, objections, CTA - leading with one promise and proving it down the page. Use when someone asks "write my landing page", "improve my hero headline", "what should the homepage say", "turn these… - 100landing-page-writer
Write full landing page copy from product info, the audience, the offer and any value proposition or positioning docs: hero headline, subhead and CTA, problem, solution, benefits, proof, objections and FAQ, and a final CTA, plus 3 headline variants to A/B test. Use when a… - 86screen
Create a product screen in Figma from a brief, reference image, or Figma URL. Use when the user asks for a screen, page, state, or flow. - 86write-the-page
Use when a page needs its words: a landing page, a product page, a headline, or copy that reads as templated. - 100understand-product
Read a product the person built - its website, repository, README, app store page, docs or a demo - and write a one-page product brief and its product type, before any launch, positioning or marketing work. Use at the start of a launch or whenever marketing work needs to know…