パックの内容

SKILL.md（手順書）1点とスターターテンプレート1点が入っています。プレビューはこちらです：

Architectural Project Deck

When to use

• You are presenting a design proposal to a client who is not an architect
• A competition or jury submission needs the project explained in a fixed slide order
• A planning or community consultation needs the scheme shown clearly to non-specialists
• A studio needs a portfolio deck for a built or in-progress project
• You are briefing consultants, contractors, or a design team on a project's intent before detailed design

Workflow

1. Gather the project material (input: drawings, renders, brief → output: project dossier)
   Collect the material the deck will draw on: the brief and site constraints, the concept statement, site and floor plans, sections, elevations, renders or models, key dimensions and areas, and the timeline and next steps. Note the status of each item (concept, developed, approved, built) — a deck must never present a concept-stage drawing as if it were approved. Flag anything missing (no site plan, no north arrow) before building slides around it.
2. Build the story arc (input: project dossier → output: slide outline)
   Order the deck as a story a non-architect can follow: site and brief → concept (one idea, stated plainly) → how the concept shapes the plan → key spaces → materials and light → timeline and next steps. Aim for 10–14 slides, one idea per slide. If the concept cannot be stated in one sentence, it is not ready for a slide — clarify it first.
3. Set the visual system (input: slide outline → output: drawing standards)
   Fix drawing standards before laying out slides: one scale note per drawing, a consistent north arrow and scale bar on every plan, one line-weight hierarchy, and one palette for annotations (for example, muted grey drawings with a single accent color for the concept moves). Every drawing gets a caption: what it is, its scale or "not to scale", and its status. Renders are labeled as renders, not photographs, when the project is unbuilt.
4. Build the slides (input: outline + standards → output: full deck draft)
   Give each slide one job. Site slides show context (location, constraints, sun, access). Concept slides show the one big idea with a simple diagram, not a paragraph. Plan slides show one drawing large, with 2–3 callouts pointing at what matters — never shrink three drawings onto one slide. Renders get breathing room: one view per slide, captioned with what the viewer is looking at. Timeline slides show phases, dates, and decisions needed, in plain language.
5. Review for a non-architect (input: deck draft → output: presentation-ready deck)
   Read the deck as the client would: is every drawing explained in words, is every piece of jargon either removed or defined, and could someone understand the project without you in the room? Check that dimensions, areas, and dates match the source drawings — a deck that disagrees with its own plans destroys credibility. Add speaker notes for anything that genuinely needs narration, and export a self-reading PDF for reviewers.

テンプレートのプレビュー

Architectural Project Deck — Build Template

One project = one deck. Confirm drawing status before presenting anything as final.

Project: {project name} — {site / client}

Audience: {client / jury / planning reviewers / consultants} Concept in one sentence: {the one idea, plainly stated} Status of the project: {concept / developed / approved / built}

Project dossier

Missing items (do not build slides around them): {list or "none"}

Slide outline (10–14 slides, story order)

Drawing standards (fixed before layout)

• North arrow + scale bar on every plan: [ ]
• Scale note per drawing (e.g., 1:100) or "not to scale": [ ]

スキルパック本体（SKILL.md とテンプレート）は英語で書かれています。

スキルパックを購入 — $4.99 Pro — 全511件のスキル