Knowledge Hub

Resources that do work

Articles, guides, playbooks, architecture patterns and a working prompt library — all drawn from the same practice that runs this site.

Articles

Thinking

Prompt Library

Copy, paste, ship

Working prompts, generalized from the engines running on this site. Try them with any capable model — or live in our Playground.

Proposal skeleton

Turn a rough project idea into a reviewable proposal structure.

You are a senior consultant. From the project description below, produce a proposal skeleton: 1) Objective in one sentence, 2) Scope — explicitly in AND out, 3) Approach in 3 phases, 4) Timeline bands (no false precision), 5) Assumptions that must be verified. Be concrete; no filler.

Project: [describe your project]

Testable requirements

Convert a feature wish into statements a QA team can verify.

Rewrite the feature description below as numbered functional requirements. Each must start with 'The system shall', contain exactly one behaviour, and be testable. Append a non-functional checklist covering performance, accessibility and security.

Feature: [describe the feature]

Meeting minutes

Rough notes → decisions, owners and open questions.

From the raw notes below, produce minutes with four sections: Decisions (what was agreed), Action items (owner → task → due), Open questions, Next meeting. Preserve facts exactly; never invent names or dates that aren't in the notes.

Notes: [paste raw notes]

SEO triage

The three fixes that matter, before the fifty that don't.

Analyze the page copy below. Return: the 3 highest-impact improvements (ranked, with reasoning), a title tag ≤60 characters that says what the page does, a meta description ≤155 characters that earns the click, and 5 keyword phrases a real person would search. No keyword stuffing.

Copy: [paste page copy]

One topic, three voices

Social drafts that respect each channel's culture.

Write about the topic below in three formats: a LinkedIn post (insight-led, no hashtag spam), an Instagram caption (warm, max 3 hashtags), a short X post (one sharp idea). Match this brand voice: [describe voice].

Topic: [your topic]

Assumption register seed

Start any project honest — from our delivery playbook.

From the project brief below, list every assumption being made — unverified statistics, access not yet confirmed, stakeholder availability, deployment targets, third-party dependencies. Format as a table: Assumption | Risk if wrong | How to verify | Suggested owner. Include the assumptions that feel 'obviously fine'; those are the dangerous ones.

Brief: [paste brief]

Coming next

The hub grows

📑 Whitepapers

Deep treatments of the Human Growth Loop and demo-mode architecture — in editorial review.

🎙️ Webinars

Live engineering walkthroughs, starting with the Builder Growth Platform. Join the newsletter below to be invited.