Skip to main content

Prompts

How long before the prompters become the prompted?

The right prompt at the right time. Mantra for yourself. Technique for the machine. Same mechanism, both directions.

The Human Prompt

When you know the subject, you can teach it. When you know the person, you can prompt them in the right direction when it matters most.

Teaching focuses on transferring knowledge about a topic, while coaching (and well-timed prompting) focuses on the person’s context, emotions, and decisions so they can find their own way forward.

The Art of Living Well

The art of living well is training yourself to see the invisible — and learning to sell why what you see matters. In practice, that's:

  1. Perceive what others miss (patterns, feelings, futures, quiet problems).
  2. Turn it into a story that helps people feel its importance.
  3. Sell it so they want to act with you.

The Creative Rhythm

Inspiration is available in every moment. The courage and the platform to act on it are ready and willing. Inspiration is now. Act anyway.

  1. Notice — pause to sense what draws your attention (a colour, a feeling, a memory).
  2. Capture — jot it down, sketch, or photograph it before the spark fades.
  3. Act — pick one small step that honours that spark now, not later.

The Agent Prompt

"The prompt" as a singular, chat-based interaction is becoming obsolete. As models evolve into autonomous agents that can work for days without human intervention, the human can no longer act as the real-time intent and quality layer. Prompting has now fractured into four distinct disciplines:

DisciplineWhat It IsGoal
Prompt CraftWriting clear instructions, guardrails, and examplesTable stakes for immediate AI responses
Context EngineeringCurating the optimal set of tokens (tools, docs, memory)Providing comprehensive information for autonomous tasks
Intent EngineeringEncoding organizational purpose and decision boundariesAligning agents with strategy to prevent the wrong optimization
Specification EngineeringWriting agent-fungible documents that agents execute againstEmbedding all necessary oversight without human intervention

Specification Primitives

To bridge the gap left by the absence of a real-time human operator, agents require embedded oversight. This relies on five specification primitives:

  1. Self-contained problem statements
  2. Acceptance criteria
  3. Constraint architecture
  4. Decomposition
  5. Evaluation design

First Principles

Prompt Engineering Five rules that apply to every modality — text, voice, image, music, video, code, games.

PrincipleWhat It DoesExample
ContextGround the model in your world"You are a senior infrastructure engineer reviewing a Terraform plan"
ConstraintNarrow the output space"Under 200 words, bullet points only, no speculation"
ExampleShow, don't describe"Input: X → Output: Y. Now do Z."
IterationRefine through feedback loops"That's close. Now make it more concise and remove the passive voice"
StructureShape the response format"Use XML tags: <analysis>, <recommendation>, <risk>"

Every technique in every star page is a combination of these five. Chain of thought = Structure + Iteration. Persona prompting = Context + Constraint. Negative prompting = Constraint applied to pixels. Same five principles, any input format to any output format — see the full modality matrix.

Capability Matrix

DomainPrompt PageArchetypeOutcomeTools
AnalysisAnalysisThe RealistInsight and patternPerplexity, Claude, Gemini
StrategyStrategyThe GeneralLeverage and planClaude, OpenAI o-series
PredictionsPredictionsThe OracleCalibrated foresightSuperforecaster frameworks
CodingCodingThe EngineerStructure and functionCursor, Copilot, Claude Code
Web DesignWeb DesignThe CraftsmanInterfaces that workv0, Bolt, Lovable
Visual ArtVisual ArtThe ArtistComposition and styleMidjourney, DALL-E, Flux
MusicMusicThe ComposerFeeling with structureSuno, Udio, Stable Audio
VideoVideoThe DirectorMotion as meaningRunway, Sora, Kling
Promo VideoPromo VideoThe AdvertiserConversion in secondsRunway, Kling, Pika, CapCut
GamesGamesThe DesignerLoops that teachUnity AI, Inworld, Scenario
VoiceCommunicationThe TranslatorSpeech and text bridgeWhisper, ElevenLabs, Deepgram, Claude Voice
CommunicationCommunicationThe MessengerInfluence and scaleGrammarly, Claude, Jasper
CreativeCreativeThe DreamerNovelty and visionAll of the above
LibraryLibraryThe LibrarianCopy, paste, iterateLLMs

Context

Questions

If the five principles work for every modality, what changes between prompting text and prompting pixels?

  • Are you teaching the subject, or are you prompting the person?
  • What invisible problem are you currently seeing that you haven't yet named or sold to others?
  • Why is "the prompt" becoming obsolete, and why is prompt craft now just table stakes?
  • What is the risk of intent misalignment when agents run autonomously for days?
  • How do the five primitives of specification engineering replace the synchronous "human-in-the-loop" quality layer?
  • When does iterating a prompt become more valuable than switching models?
  • Which capability in the matrix above do you use daily vs which do you avoid — and what does that gap cost you?
  • If prompting is alignment in both directions (you to machine, mantra to you), which direction are you worse at?