landing-page-pillar-management skill: it drafts a data schema plus
a generation prompt that together define a whole type of landing page, so you can produce many similar
pages programmatically. Build horizontal pillars (/uses, /use-cases, /industry) first for reach,
then vertical ones (/feature, /product, /integration) for depth. Draw the fan-out facets from the
Product Bible, not a keyword tool, and keep them
non-overlapping so pages don’t cannibalize. Once the pillar exists,
generate pages against it. Read
Part 1 §1.6 pillars first for the wide-before-deep model.
Horizontal vs vertical
- Horizontal pillars (
/uses,/use-cases,/industry) go wide across use-cases. Build these first: higher volume, easier to build. - Vertical pillars (
/feature,/product,/integration) go deep on one feature. Build them once the wide net is cast.
Design it with Pi
Use thelanding-page-pillar-management skill. The sequence that works:
- Plan the pillar (Pi drafts the schema + generation prompt; the default template is usually a good start).
- Visualize in ASCII and iterate until the structure is right.
- Create a sample page to sanity-check the output.
- Create the pillar once you’re happy.