
Architectural Project Deckv1.0.0
Use this Skill to create presentation.
Create an architectural project presentation with site logic, spatial sequencing, material evidence, and review-ready annotations. It keeps plans and design decisions legible while clearly separating preliminary communication from professional approval.
Picked most often by
Updated Aug 30, 2026
Preview gallery
Runs in
Generates with
Similar Skills
View all skillsWhat you get
- A self-contained architectural review deck with plans, diagrams, materials, and phased evidence.
- A project-specific layout library that keeps one dominant architectural artifact per slide.
- Visible assumptions, revision data, professional boundaries, and browser QA guidance.
Good fit
- Concept design and client reviews that need a clear spatial argument.
- Interior or development teams presenting site, massing, materials, and phasing.
- Projects with rights-cleared drawings and explicit known-versus-assumed data.
Not for
- Code, zoning, structural, cost, or constructability approval.
- Construction-document coordination or precise BIM exchange.
- Decks whose measurements or source revisions cannot be reconciled.
About this Skill

Architectural Project Deck Guide
What this Skill makes
A self-contained architectural presentation that advances one spatial argument per slide through plans, massing, material evidence, program, phasing, and review annotations.
Before you start
Provide the project phase, audience, review question, slide count, consistent units, drawing revisions, rights-cleared evidence, known assumptions, and professional disclaimer.
Build
Normalize the evidence before composing. Choose one named material theme, give each page a single dominant artifact, and use concise insight-led headings. Keep the shared horizontal engine intact and key notes by semantic slide id.
Review
Cross-check each dimension and revision, inspect every page in Chrome, exercise paging, overview and notes, verify narrow and print behavior, and confirm no external dependency or console error.
Handoff
Deliver the deck path, normalized evidence ledger, assumptions, revision, professional boundary, chosen theme, and exact QA completed.
What you need before you start
- You bring
- Project brief, phase, review audience, and decision goal · Rights-cleared site facts, plans, sections, program, or material data · Known assumptions, revision information, and professional disclaimer
- Dependencies
- Modern browser — required · Node.js 20 or newer — required for validation
- Last tested
- v1.0.0 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT
User reviews
Loading reviews…









