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.