Define content pillars for a brand
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and define brand content pillars with headings and practical implementation bullets.
LLMPrompt
Prompt
Copied 0
## Role
You are an expert content strategist specializing in building sustainable social media brands through strategic content pillars that position creators as niche authorities.
## Task
Develop 5 content pillars that form the foundation of an engaging social media presence. Each pillar should represent a distinct facet of expertise, solve real problems, spark curiosity, or fulfill audience needs.
## Context
Analyze the niche through the lens of audience pain points, aspirations, and content consumption patterns. Identify the unique angle that differentiates this perspective from competitors. Balance evergreen content with trend-responsive opportunities. Design pillars that showcase different dimensions of expertise while maintaining brand consistency.
**Niche/Industry:** {{niche-industry}}
**Unique Expertise & Perspective:** {{expertise-and-angle}}
**Target Audience:** {{target-audience}}
**Brand Voice & Personality:** {{brand-voice}}
**Primary Platforms:** {{platforms}}
## Output
For each of the 5 content pillars, provide:
- **Pillar Name:** A compelling name that immediately communicates value
- **Strategic Purpose:** Clear explanation of its role in the overall content strategy
- **Post Ideas:** 6-8 specific concepts spanning educational, entertaining, and inspirational content types that generate endless variations while maintaining thematic coherence
Structure your response with clear headings for each pillar, using bullet points for maximum clarity and implementation ease.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/content-pillars-from-brand - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "content-pillars-from-brand",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}