hangar

Use when building or recreating a Planes-style presentation deck: a playback, pitch, demo, strategy or client deck in the studio's house design (the "big playback deck" look people liked). Also use when someone wants an on-brand HTML slide deck with Planes fonts, colours, transitions and layouts, or asks to "make a deck like the Lewis Silkin playback" or "build a deck in the Planes style".

Use when building or recreating a Planes-style presentation deck: a playback, pitch, demo, strategy or client deck in the studio's house design (the "big playback deck" look people liked). Also use when someone wants an on-brand HTML slide deck with Planes fonts, colours, transitions and layouts, or asks to "make a deck like the Lewis Silkin playback" or "build a deck in the Planes style".

Use when writing, rewriting, or reviewing any copy that should sound like Planes: pitch decks, proposals, playbacks, credentials and RFP responses, website and product copy, case studies, emails, taglines, headlines, or any client-facing or internal writing that needs to be on brand. Also use when copy reads generic, corporate, hypey, or off-voice and someone wants it to "sound like us" or "sound like Planes".

Use when writing, rewriting, or reviewing any copy that should sound like Planes: pitch decks, proposals, playbacks, credentials and RFP responses, website and product copy, case studies, emails, taglines, headlines, or any client-facing or internal writing that needs to be on brand. Also use when copy reads generic, corporate, hypey, or off-voice and someone wants it to "sound like us" or "sound like Planes".

Designs a collaborative workshop and builds it as a ready-to-run FigJam board, plus a facilitator run-sheet and a participant invite email. Use this skill whenever Fiona (or anyone at Planes) wants to plan, design, structure, or build a workshop, session, or facilitated meeting — and especially whenever FigJam is mentioned. Trigger on phrases like "create a workshop", "design a workshop", "build a FigJam board", "set up a workshop in FigJam", "I'm running a session with [client]", "plan a discovery workshop", "kickoff workshop", "ideation session", "retro board", "prioritisation workshop", "journey mapping session", "we need a workshop for X", "turn this into a FigJam", or any request to prepare a participatory session. Always use this skill for workshop design even if the person doesn't say "FigJam" explicitly — it produces the agenda, the board, the run-sheet, and the invite together so the whole session is ready to facilitate.

Designs a collaborative workshop and builds it as a ready-to-run FigJam board, plus a facilitator run-sheet and a participant invite email. Use this skill whenever Fiona (or anyone at Planes) wants to plan, design, structure, or build a workshop, session, or facilitated meeting — and especially whenever FigJam is mentioned. Trigger on phrases like "create a workshop", "design a workshop", "build a FigJam board", "set up a workshop in FigJam", "I'm running a session with [client]", "plan a discovery workshop", "kickoff workshop", "ideation session", "retro board", "prioritisation workshop", "journey mapping session", "we need a workshop for X", "turn this into a FigJam", or any request to prepare a participatory session. Always use this skill for workshop design even if the person doesn't say "FigJam" explicitly — it produces the agenda, the board, the run-sheet, and the invite together so the whole session is ready to facilitate.

Estimate the ongoing third-party running costs for a software product or build and write it up as a structured Notion page. Use whenever someone at Planes wants to scope what a build will cost to run: "ongoing costs", "running costs", "hosting costs", "what would it cost to run", "cost estimate for [client]", "infrastructure costs", "third-party costs", "platform costs", "put together a quote for running X", "how much will the stack cost", or when a client asks for cost estimates for a new product or feature. Trigger even if no specific service is named and even if they only describe the product. It asks what is being built, proposes a stack the user can edit, researches current pricing live, models light/moderate/heavy scenarios and cost thresholds, and writes it up in Notion with sources. Do NOT use for one-off "what does service X cost" lookups, for invoicing money already spent, or for Planes' own internal SaaS spend.

Estimate the ongoing third-party running costs for a software product or build and write it up as a structured Notion page. Use whenever someone at Planes wants to scope what a build will cost to run: "ongoing costs", "running costs", "hosting costs", "what would it cost to run", "cost estimate for [client]", "infrastructure costs", "third-party costs", "platform costs", "put together a quote for running X", "how much will the stack cost", or when a client asks for cost estimates for a new product or feature. Trigger even if no specific service is named and even if they only describe the product. It asks what is being built, proposes a stack the user can edit, researches current pricing live, models light/moderate/heavy scenarios and cost thresholds, and writes it up in Notion with sources. Do NOT use for one-off "what does service X cost" lookups, for invoicing money already spent, or for Planes' own internal SaaS spend.

Use this skill whenever a Planes team member wants to reflect on their professional development, understand their strengths, identify growth areas, or set progression goals. Trigger on any of: "what are my superpowers", "where should I focus my growth", "help me with my progression goals", "can you review my feedback cycles", "I want to think about my career at Planes", "what level am I performing at", "help me prepare for my team growth meeting", "I want to understand my development", "what should I be working on to get promoted", or any request that involves understanding personal performance or career progression at Planes. This skill fetches the live Planes Notion pages for context — always use it rather than trying to answer career/growth questions from memory.

Synthesize a user interview transcript into a thematic analysis, output as a ready-to-import FigJam plugin (horizontal theme bands across the top, a participant card on the left, a row of color-coded insight stickies under each theme, and yellow verbatim-quote stickies sitting DIRECTLY BELOW each insight connected by a straight downward arrow) AND a structured markdown text file with the same content so multiple interviews can be combined later. Use this skill whenever the user mentions research synthesis, user interviews, thematic analysis, affinity mapping, insight extraction, discussion guides, FigJam boards for research, "synthesize this interview", "make a research board", "pull themes out of this transcript", or any task that involves turning raw interview content into a structured visual + text summary. Also trigger when the user mentions Granola meetings in a research context.

Show a rundown of the skills most recently added to The Hangar, what each does and how to run it, so you know what you just got after a plugin update.

You are an expert copy editor specializing in marketing and conversion copy. Your goal is to systematically improve existing copy through focused editing passes while preserving the core message.

Turns a loose project intake into a sharp, Planes-style design brief. Opinionated. Single-pager. Ready to share with the team and the client.

Get a structured, numbered critique of a UI with specific, actionable feedback across hierarchy, clarity, consistency, and accessibility.

Systematic debugging, state the error, form hypotheses in order of likelihood, and test each one before jumping to a fix.

A two-pass PR review with Claude that catches the boring stuff *and* asks the questions a senior engineer at Planes would actually ask.

Turns Claude into the colleague who asks the awkward question. Useful when you're about to commit to a direction and want one more pass before you do.

Rewrite a draft email to be clearer, shorter, and more likely to get a reply.

Strip the tells out of AI-generated writing so it reads like a person wrote it. Catches inflated significance, promotional language, rule-of-three, AI vocabulary, em dash overuse, and 25 other patterns.

Get a structured devil's advocate on any decision, plan, or proposal, what you might be missing, what could go wrong, and what a smart critic would say.

Generate 10 genuinely unusual name options for anything, products, features, projects, teams, with a brief rationale for each.

Structure a client project as a compelling, shareable case study, with a clear problem, an honest account of the work, and a result worth citing.

Write a sharp, human cold introduction email for a new prospect, specific, brief, and worth replying to.

Drafts the credentials section of an RFP response in Planes' voice. Confident, specific, grounded in named work, without sliding into agency-speak.

You are an expert in experimentation and A/B testing. Your goal is to help design tests that produce statistically valid, actionable results.

You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.

You are an expert customer researcher. Your goal is to help uncover what customers actually think, feel, say, and struggle with, so that everything from positioning to product to copy is grounded in reality rather than assumption.

You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.

Turn a vague problem description into a sharp, well-scoped statement with user context, root cause, and a measurable success signal.

Takes a stack of raw user interview transcripts and pulls out Jobs To Be Done in the format Planes uses. Situation-led, in the user's own language, with quoted evidence.

Paste raw interview notes and get structured themes, supporting quotes, tensions, and recommended next steps.