Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.
When to Activate
drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues
turning notes, transcripts, or research into polished articles
matching an existing founder, operator, or brand voice from examples
tightening structure, pacing, and evidence in already-written long-form copy
Core Rules
Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.
Explain after the example, not before.
Keep sentences tight unless the source voice is intentionally expansive.
Use proof instead of adjectives.
Never invent facts, credibility, or customer evidence.
Voice Handling
If the user wants a specific voice, run brand-voice first and reuse its VOICE PROFILE. Do not duplicate a second style-analysis pass here unless the user explicitly asks for one.
If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.
Banned Patterns
Delete and rewrite any of these:
"In today's rapidly evolving landscape"
"game-changer", "cutting-edge", "revolutionary"
"here's why this matters" as a standalone bridge
fake vulnerability arcs
a closing question added only to juice engagement
biography padding that does not move the argument
generic AI throat-clearing that delays the point
Writing Process
Clarify the audience and purpose.
Build a hard outline with one job per section.
Start sections with proof, artifact, conflict, or example.
Expand only where the next sentence earns space.
Cut anything that sounds templated, overexplained, or self-congratulatory.
Structure Guidance
Technical Guides
open with what the reader gets
use code, commands, screenshots, or concrete output in major sections
end with actionable takeaways, not a soft recap
Essays / Opinion
start with tension, contradiction, or a specific observation
keep one argument thread per section
make opinions answer to evidence
Newsletters
keep the first screen doing real work
do not front-load diary filler
use section labels only when they improve scanability
Quality Gate
Before delivering:
factual claims are backed by provided sources
generic AI transitions are gone
the voice matches the supplied examples or the agreed VOICE PROFILE
docker-patternsaffaan-mDocker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.4,8004,800 instalaciones en skills.sh0
security-reviewaffaan-mUse this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.4,8004,800 instalaciones en skills.sh0
backend-patternsaffaan-mBackend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.4,7004,700 instalaciones en skills.sh0
frontend-patternsaffaan-mFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.4,7004,700 instalaciones en skills.sh0
coding-standardsaffaan-mBaseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.4,5004,500 instalaciones en skills.sh0
