Templates & Frameworks Design Prompts¶

Comprehensive prompt templates for business documents, proposals, reports, invoices, and reusable framework designs

Created: February 2026 Tool: Nano Banana Pro / Document Studio Related: Framework Overview | Documents | Presentations

Design System Configuration¶

# PARAMETERIZED DESIGN SYSTEM INTEGRATION
# This file inherits from the parent design system framework
# See: ./readme.md for complete token definitions and variant specifications

design_system:
  parent_config: "./readme.md"
  schema_version: "2.0"
  category: "templates_frameworks"

  # Default template configuration
  default_variant: "trusted_advisor"
  default_grid: "structured_grid"
  default_frame: "frame_solid"

  # Template-specific token mappings
  tokens:
    # Color tokens (resolve from active variant)
    colors:
      primary: "{{colors.primary}}"
      secondary: "{{colors.secondary}}"
      accent: "{{colors.accent}}"
      background: "{{colors.background}}"
      surface: "{{colors.surface}}"
      text_primary: "{{colors.text_primary}}"
      text_secondary: "{{colors.text_secondary}}"
      border: "{{colors.border}}"
      success: "{{colors.success}}"
      warning: "{{colors.warning}}"
      error: "{{colors.error}}"

    # Typography tokens
    typography:
      heading_font: "{{typography.heading_font}}"
      body_font: "{{typography.body_font}}"
      mono_font: "{{typography.mono_font}}"
      heading_weight: "{{typography.heading_weight}}"
      body_weight: "{{typography.body_weight}}"

    # Spacing & sizing tokens
    spacing:
      page_margin: "{{spacing.space_6}}"
      section_gap: "{{spacing.space_8}}"
      paragraph_gap: "{{spacing.space_4}}"
      header_height: "{{spacing.space_16}}"
      footer_height: "{{spacing.space_12}}"

    # Visual tokens
    visual:
      border_radius: "{{sizing_tokens.radius_lg}}"
      shadow: "{{shadow_tokens.shadow_md}}"
      border_width: "{{sizing_tokens.border_1}}"

  # Variant recommendations by template type
  variant_recommendations:
    business_documents:
      primary: "trusted_advisor"
      alternatives: ["clean_developer", "modern_partner"]
      rationale: "Professional stability and established expertise for formal business communications"
      grid_system: "structured_grid"
      frame_style: "frame_solid"

    proposals:
      primary: "bold_challenger"
      alternatives: ["trusted_advisor", "modern_partner"]
      rationale: "Confident differentiation that stands out in competitive situations"
      grid_system: "structured_grid"
      frame_style: "frame_solid"

    reports:
      assessment: "cyber_shield"
      security: "sentinel_guard"
      executive: "trusted_advisor"
      technical: "blueprint_technical"
      rationale: "Match report type to appropriate visual authority"
      grid_system: "technical_grid"
      frame_style: "frame_solid"

    invoices_financial:
      primary: "clean_developer"
      alternatives: ["trusted_advisor"]
      rationale: "Clean precision for financial accuracy and professionalism"
      grid_system: "structured_grid"
      frame_style: "frame_solid"

    operational_templates:
      primary: "modern_partner"
      alternatives: ["trusted_advisor", "clean_developer"]
      rationale: "Collaborative warmth for internal and client-facing operations"
      grid_system: "subtle_grid"
      frame_style: "frame_solid"

    technical_documentation:
      primary: "blueprint_technical"
      alternatives: ["clean_developer", "cyber_shield"]
      rationale: "Engineering precision for specifications and technical content"
      grid_system: "technical_grid"
      frame_style: "frame_dashed"

  # Grid system references
  grid_systems:
    minimal_grid:
      description: "No visible grid, pure content focus"
      use_cases: ["letters", "simple communications"]
      outer_frame: false
      inner_dividers: false

    subtle_grid:
      description: "Barely visible structure for sophisticated layouts"
      use_cases: ["proposals", "executive documents"]
      outer_frame: "{{frame_tokens.frame_solid}}"
      outer_opacity: 0.1
      inner_dividers: "{{frame_tokens.frame_dotted}}"
      inner_opacity: 0.05

    structured_grid:
      description: "Clear structure for data-heavy layouts"
      use_cases: ["invoices", "status reports", "budgets"]
      outer_frame: "{{frame_tokens.frame_solid}}"
      outer_opacity: 0.2
      inner_dividers: "{{frame_tokens.frame_solid}}"
      inner_opacity: 0.1

    technical_grid:
      description: "Blueprint/technical drawing aesthetic"
      use_cases: ["technical proposals", "specifications", "architecture documents"]
      outer_frame: "{{frame_tokens.frame_solid}}"
      outer_opacity: 0.3
      inner_dividers: "{{frame_tokens.frame_dashed}}"
      inner_opacity: 0.15
      corner_marks: true

    editorial_grid:
      description: "Magazine/editorial layout structure"
      use_cases: ["QBR presentations", "annual reports", "case studies"]
      outer_frame: "{{frame_tokens.frame_double}}"
      outer_opacity: 0.15
      inner_dividers: "{{frame_tokens.frame_solid}}"
      column_rules: true

    dashboard_grid:
      description: "Card-based dashboard layouts"
      use_cases: ["status dashboards", "metric reports", "KPI summaries"]
      cell_borders: "{{frame_tokens.frame_solid}}"
      cell_opacity: 0.12
      cell_radius: "{{sizing_tokens.radius_lg}}"

    cyber_grid:
      description: "Security/cyber operations aesthetic"
      use_cases: ["security assessments", "threat reports", "incident documentation"]
      outer_frame: "{{frame_tokens.frame_glow}}"
      outer_opacity: 0.4
      scan_lines: true
      corner_brackets: true

  # Frame style options
  frame_styles:
    solid:
      token: "{{frame_tokens.frame_solid}}"
      description: "Clean solid lines for professional structure"
      use_cases: ["formal documents", "contracts", "official communications"]

    dotted:
      token: "{{frame_tokens.frame_dotted}}"
      description: "Subtle dotted lines for technical/draft feel"
      use_cases: ["draft documents", "annotation guides", "flexible layouts"]

    dashed:
      token: "{{frame_tokens.frame_dashed}}"
      description: "Dashed lines for dynamic structure"
      use_cases: ["action items", "selection areas", "editable zones"]

    double:
      token: "{{frame_tokens.frame_double}}"
      description: "Double lines for emphasis and premium feel"
      use_cases: ["certificates", "premium proposals", "executive summaries"]

    gradient:
      token: "{{frame_tokens.frame_gradient}}"
      description: "Gradient borders for modern/dynamic feel"
      use_cases: ["creative proposals", "marketing materials", "featured content"]

    glow:
      token: "{{frame_tokens.frame_glow}}"
      description: "Subtle glow effect for tech/cyber aesthetic"
      use_cases: ["security documents", "tech proposals", "innovation content"]

Blueprint Technical Variant Notes¶

# BLUEPRINT_TECHNICAL VARIANT - Special Implementation Notes
# AlignUI-inspired engineering drawing aesthetic
# Primary colors: #1C1C1C (Charcoal) + #F05023 (Engineering Orange)

blueprint_technical:
  id: "blueprint_technical"
  name: "Blueprint Technical"
  description: "Engineering drawing aesthetic for technical precision and specification clarity"
  inspiration: "AlignUI design system, CAD documentation, engineering blueprints"

  colors:
    primary: "#1C1C1C"              # Engineering Charcoal
    accent: "#F05023"               # Engineering Orange
    background: "#FAFAFA"           # Technical Paper
    grid_line: "#E5E5E5"            # Construction Grid
    annotation: "#666666"           # Dimension Text

  # Technical documentation templates
  template_applications:
    technical_proposals:
      description: "Engineering approach proposals with specification tables"
      grid: "technical_grid"
      frame: "frame_dashed"
      features:
        - "Dimension annotation styling"
        - "Specification callout boxes"
        - "Reference grid overlay"
        - "Section markers (A-1, B-2, etc.)"

    engineering_specifications:
      description: "Detailed technical specifications and requirements"
      grid: "technical_grid"
      frame: "frame_solid"
      features:
        - "Parameter tables with units"
        - "Tolerance indicators"
        - "Revision tracking blocks"
        - "Cross-reference markers"

    architecture_documents:
      description: "System architecture and infrastructure documentation"
      grid: "technical_grid"
      frame: "frame_dashed"
      features:
        - "Component callouts"
        - "Connection path annotations"
        - "Scale indicators"
        - "Layer references"

    cad_annotation_styles:
      description: "CAD-style annotation patterns for diagrams"
      elements:
        dimension_lines:
          style: "{{frame_tokens.frame_solid}}"
          weight: "1px"
          end_marks: "tick"           # Options: tick, arrow, dot, none
          offset: "{{spacing.space_2}}"

        leader_lines:
          style: "{{frame_tokens.frame_solid}}"
          weight: "1px"
          end_marks: "arrow"
          bend_style: "orthogonal"    # Options: orthogonal, diagonal, curved

        callout_boxes:
          frame: "{{frame_tokens.frame_solid}}"
          background: "{{colors.surface}}"
          corner_radius: "{{sizing_tokens.radius_sm}}"
          connector: "leader_line"

        section_markers:
          shape: "circle"
          size: "24px"
          frame: "{{frame_tokens.frame_solid}}"
          weight: "2px"
          fill: "{{colors.background}}"
          label_font: "{{typography.mono_font}}"
          label_weight: "{{typography.weight_bold}}"

        revision_clouds:
          style: "scalloped"
          color: "{{colors.accent}}"
          weight: "1px"
          spacing: "8px"

        grid_references:
          format: "A-1, B-2, C-3"
          position: "corner"
          font: "{{typography.mono_font}}"
          size: "{{typography.text_xs}}"

  # Typography for technical documents
  typography:
    heading_font: "{{font_primary}}"
    body_font: "{{font_primary}}"
    annotation_font: "{{font_mono}}"
    dimension_font: "{{font_mono}}"
    weights:
      title: "{{weight_bold}}"
      section: "{{weight_semibold}}"
      body: "{{weight_regular}}"
      annotation: "{{weight_medium}}"

  # Grid specifications
  grid_specifications:
    major_grid:
      spacing: "48px"
      color: "{{grid_line}}"
      opacity: 0.3
      style: "{{frame_tokens.frame_solid}}"

    minor_grid:
      spacing: "12px"
      color: "{{grid_line}}"
      opacity: 0.1
      style: "{{frame_tokens.frame_dotted}}"

    construction_lines:
      color: "{{accent}}"
      opacity: 0.2
      style: "{{frame_tokens.frame_dashed}}"

  # Prompt prefix for blueprint technical variant
  prompt_prefix: |
    [STYLE: BLUEPRINT TECHNICAL]
    Color palette: Engineering charcoal (#1C1C1C) with orange (#F05023) accents on technical paper (#FAFAFA).
    Mood: Engineering precision, CAD-quality documentation, specification clarity.
    Texture: Subtle technical grid overlay, construction line references.
    Typography: Monospace for dimensions and annotations, clean sans for body.
    Grid: Visible construction grid with major/minor divisions.
    Annotations: CAD-style dimension lines, leader callouts, section markers.
    Corners: Precise right angles, minimal radius (2px max).
    Frame: Dashed construction lines for editable areas, solid for fixed.

Templates Philosophy¶

SBK templates must: - Accelerate delivery through consistent, reusable structures - Maintain brand integrity across all touchpoints - Reduce cognitive load for both creators and recipients - Enable customization without compromising quality - Scale effectively across team members and projects

Template Anti-Patterns¶

Never create: - Overly rigid templates that prevent necessary customization - Inconsistent formatting between template versions - Templates that become outdated without version control - Complex templates requiring extensive training to use - Templates that prioritize aesthetics over functionality

Proposal Templates¶

Executive Proposal¶

# DESIGN SYSTEM INTEGRATION
variant: "{{variant_recommendations.proposals.primary}}"  # bold_challenger
grid_system: "{{variant_recommendations.proposals.grid_system}}"  # structured_grid
frame_style: "{{variant_recommendations.proposals.frame_style}}"  # frame_solid
alternatives: ["trusted_advisor", "modern_partner"]

[SBK BRAND DNA]
Professional technology consulting. Persuasive, clear, action-oriented.
Typography: {{typography.heading_font}} for headings, {{typography.body_font}} for body.
Primary color: {{colors.primary}} with {{colors.accent}} accents.

[ASSET: TEMPLATE - EXECUTIVE PROPOSAL]
High-level proposal for executive decision-makers.

[DOCUMENT STRUCTURE]
Cover page:
  - Client company name.
  - Proposal title.
  - Date.
  - SBK logo and contact.
  - Confidentiality notice.
  - Background: {{colors.background}} with {{colors.primary}} accent bar.

Executive summary (1 page max):
  - Challenge overview.
  - Proposed solution.
  - Key outcomes.
  - Investment summary.
  - Recommended next steps.
  - Callout box: {{colors.surface}} with {{frame_styles.solid.token}} border.

Understanding of needs (1-2 pages):
  - Current state assessment.
  - Key pain points identified.
  - Business impact of challenges.
  - Success criteria defined.

Proposed approach (2-4 pages):
  - Methodology overview.
  - Phase breakdown.
  - Deliverables per phase.
  - Timeline summary.
  - Team introduction.
  - Timeline visual: {{grid_systems.structured_grid}} layout.

Investment (1-2 pages):
  - Pricing structure.
  - Payment terms.
  - What's included/excluded.
  - Optional add-ons.
  - Pricing table: {{frame_styles.solid.token}} borders at {{grid_systems.structured_grid.outer_opacity}}.

Why SBK (1 page):
  - Relevant experience.
  - Key differentiators.
  - Client testimonials.
  - Case study highlights.

Next steps (1 page):
  - Acceptance process.
  - Start date options.
  - Contact information.
  - Signature block.
  - CTA section: {{colors.accent}} highlight.

Appendices:
  - Detailed scope.
  - Team bios.
  - Case studies.
  - Terms and conditions.

[SPECIFICATIONS]
Format: Word (.docx) and PDF.
Length: 8-15 pages main body.
Paper: Letter (8.5x11") or A4.
Margins: {{spacing.page_margin}}.
Font: {{typography.body_font}}, {{typography.text_base}} body.

[DESIGN ELEMENTS]
Header: SBK logo, page number. Height: {{spacing.header_height}}.
Footer: Confidentiality, proposal date. Height: {{spacing.footer_height}}.
Colors: {{colors.primary}}, {{colors.secondary}}, {{colors.accent}}.
Graphics: Charts, diagrams, icons in {{colors.primary}} palette.
White space: {{spacing.section_gap}} between major sections.
Border radius: {{visual.border_radius}} on callout boxes.
Shadow: {{visual.shadow}} on elevated elements.

[GRID & FRAME]
Grid system: {{grid_systems.structured_grid.description}}
Frame style: {{frame_styles.solid.token}}
Table borders: {{visual.border_width}} {{colors.border}}
Section dividers: {{frame_styles.solid.token}} at 10% opacity

[CUSTOMIZATION ZONES]
Client logo: Optional co-branding.
Service-specific: Pillar color accent via {{colors.accent}}.
Industry: Relevant imagery/examples.
Scope: Modular sections.

Technical Proposal¶

# DESIGN SYSTEM INTEGRATION
variant: "blueprint_technical"  # Engineering precision for technical content
grid_system: "technical_grid"
frame_style: "frame_dashed"
alternatives: ["clean_developer", "cyber_shield"]

[ASSET: TEMPLATE - TECHNICAL PROPOSAL]
Detailed technical approach for implementation.
Variant: blueprint_technical for CAD-quality technical documentation.

[DOCUMENT STRUCTURE]
Cover page: Standard proposal cover with {{blueprint_technical.colors.primary}} accents.

Technical summary:
  - Technology overview.
  - Architecture summary.
  - Key components.
  - Integration points.
  - Visual: System overview diagram with {{blueprint_technical.cad_annotation_styles.section_markers}}.

Current state analysis:
  - Existing infrastructure.
  - Technology inventory.
  - Gap analysis.
  - Risk assessment.
  - Visual: Gap matrix using {{grid_systems.technical_grid}}.

Proposed solution:
  - Recommended architecture.
  - Technology stack.
  - Component specifications.
  - Integration approach.
  - Diagrams: {{blueprint_technical.cad_annotation_styles.callout_boxes}} for component details.

Implementation plan:
  - Detailed phases.
  - Sprint/milestone breakdown.
  - Resource allocation.
  - Dependencies.
  - Timeline: Gantt-style with {{frame_styles.dashed.token}} phase dividers.

Technical specifications:
  - System requirements.
  - Performance criteria.
  - Security considerations.
  - Compliance requirements.
  - Tables: {{blueprint_technical.cad_annotation_styles.dimension_lines}} styling for specs.

Risk and mitigation:
  - Technical risks.
  - Mitigation strategies.
  - Contingency plans.
  - Callouts: {{blueprint_technical.colors.accent}} for critical items.

Deliverables:
  - Documentation.
  - Source code/configuration.
  - Training materials.
  - Support documentation.

[SPECIFICATIONS]
Length: 15-30 pages.
Diagrams: Architecture, flow, network with {{blueprint_technical.grid_specifications}}.
Tables: Specifications with {{typography.annotation_font}} for values.
Appendices: Detailed technical specs.
Font: {{blueprint_technical.typography.annotation_font}} for technical content.

[GRID & FRAME]
Grid system: {{grid_systems.technical_grid.description}}
Major grid: {{blueprint_technical.grid_specifications.major_grid.spacing}} spacing
Minor grid: {{blueprint_technical.grid_specifications.minor_grid.spacing}} spacing
Frame style: {{frame_styles.dashed.token}} for editable zones
Corner marks: Enabled per {{grid_systems.technical_grid.corner_marks}}
Section markers: {{blueprint_technical.cad_annotation_styles.grid_references.format}}

Statement of Work (SOW)¶

# DESIGN SYSTEM INTEGRATION
variant: "trusted_advisor"  # Professional stability for contractual documents
grid_system: "structured_grid"
frame_style: "frame_solid"
alternatives: ["clean_developer"]

[ASSET: TEMPLATE - SOW]
Contractual statement of work.
Variant: trusted_advisor for established, reliable contract documents.

[DOCUMENT STRUCTURE]
Header section:
  - Project name.
  - Client and vendor details.
  - SOW effective date.
  - Reference to MSA.
  - Header bar: {{colors.primary}} accent line.

Project overview:
  - Background and context.
  - Project objectives.
  - Success criteria.
  - Out of scope (explicit).
  - Callout: {{colors.warning}} for out-of-scope items.

Scope of services:
  - Detailed deliverables.
  - Task breakdown.
  - Acceptance criteria per deliverable.
  - Change order process.
  - Tables: {{grid_systems.structured_grid}} with {{frame_styles.solid.token}}.

Timeline and milestones:
  - Project phases.
  - Key milestones.
  - Deliverable due dates.
  - Review periods.
  - Visual: Timeline using {{colors.primary}} phase markers.

Pricing and payment:
  - Fee structure.
  - Payment schedule.
  - Expense policy.
  - Invoicing terms.
  - Tables: {{typography.mono_font}} for currency values.

Resources and responsibilities:
  - SBK team members.
  - Client responsibilities.
  - Access requirements.
  - Communication plan.

Governance:
  - Project management approach.
  - Status reporting.
  - Escalation procedures.
  - Change management.

Terms:
  - Reference to MSA terms.
  - SOW-specific terms.
  - Termination provisions.
  - Signature blocks.
  - Signature area: {{frame_styles.solid.token}} border box.

[SPECIFICATIONS]
Format: Word and PDF.
Length: 5-15 pages.
Legal review: Required before client delivery.
Version control: Track revisions.
Margins: {{spacing.page_margin}}.
Font: {{typography.body_font}} at {{typography.text_base}}.

[GRID & FRAME]
Grid system: {{grid_systems.structured_grid.description}}
Frame style: {{frame_styles.solid.token}}
Table borders: {{visual.border_width}} {{colors.border}}
Section spacing: {{spacing.section_gap}}

Report Templates¶

Assessment Report¶

# DESIGN SYSTEM INTEGRATION
variant: "cyber_shield"  # Security operations aesthetic for assessments
grid_system: "cyber_grid"
frame_style: "frame_glow"
alternatives: ["sentinel_guard", "blueprint_technical"]
# Use sentinel_guard for AI/ML security, blueprint_technical for infrastructure assessments

[ASSET: TEMPLATE - ASSESSMENT REPORT]
Security, compliance, or technical assessment.
Variant: cyber_shield for threat-focused, security operations aesthetic.

[DOCUMENT STRUCTURE]
Cover page:
  - Assessment type.
  - Client name.
  - Report date.
  - Classification level.
  - Background: {{colors.background}} (#0a0a0b).
  - Accent: {{colors.primary}} (#dc2626) classification banner.

Executive summary:
  - Overall findings.
  - Risk rating.
  - Priority recommendations.
  - Compliance status.
  - Risk gauge: {{colors.error}} / {{colors.warning}} / {{colors.success}} indicators.

Methodology:
  - Assessment framework.
  - Scope and limitations.
  - Tools and techniques.
  - Time period.
  - Visual: Scope diagram with {{grid_systems.cyber_grid}} overlay.

Findings detail:
  - Finding ID and title.
  - Severity/risk rating.
  - Description.
  - Evidence.
  - Impact analysis.
  - Recommendation.
  - Remediation steps.
  - References.
  - Finding cards: {{frame_styles.glow.token}} border with severity-based {{colors.error}}/{{colors.warning}} glow.

Summary matrices:
  - Findings by severity.
  - Findings by category.
  - Remediation timeline.
  - Risk heat map.
  - Visuals: {{grid_systems.dashboard_grid}} for metric cards.

Appendices:
  - Detailed evidence.
  - Tool outputs.
  - Reference materials.
  - Glossary.
  - Code blocks: {{typography.mono_font}} on {{colors.surface}} background.

[SEVERITY RATINGS]
Critical: {{colors.error}} - Immediate action required.
High: #f97316 (orange) - Address within 30 days.
Medium: {{colors.warning}} - Address within 90 days.
Low: {{colors.info}} - Address when possible.
Informational: {{colors.text_secondary}} - Awareness only.

[SPECIFICATIONS]
Format: Word and PDF.
Length: Variable based on scope.
Classification: Client-specific marking.
Retention: Per client agreement.
Dark mode: Enabled per {{cyber_shield.visual.dark_mode}}.

[GRID & FRAME]
Grid system: {{grid_systems.cyber_grid.description}}
Frame style: {{frame_styles.glow.token}}
Corner brackets: {{grid_systems.cyber_grid.corner_brackets}}
Scan lines: {{grid_systems.cyber_grid.scan_lines}} at 2% opacity
Glow effect: {{frame_tokens.frame_glow.glow_radius}} on severity indicators

Project Status Report¶

# DESIGN SYSTEM INTEGRATION
variant: "modern_partner"  # Collaborative warmth for ongoing client communications
grid_system: "dashboard_grid"
frame_style: "frame_solid"
alternatives: ["trusted_advisor", "clean_developer"]

[ASSET: TEMPLATE - STATUS REPORT]
Regular project update communication.
Variant: modern_partner for collaborative, approachable updates.

[DOCUMENT STRUCTURE]
Header:
  - Project name.
  - Reporting period.
  - Report date.
  - Overall status (Green/Yellow/Red).
  - Status badge: {{colors.success}}/{{colors.warning}}/{{colors.error}} indicator.

Executive summary:
  - Key accomplishments.
  - Current focus.
  - Upcoming milestones.
  - Escalations/blockers.
  - Summary card: {{colors.surface}} with {{visual.shadow}}.

Progress detail:
  - Milestone status.
  - Tasks completed.
  - Tasks in progress.
  - Upcoming tasks.
  - Progress bars: {{colors.primary}} fill on {{colors.border}} track.

Schedule:
  - Timeline view.
  - Variance analysis.
  - Critical path status.
  - Forecast.
  - Gantt visual: {{colors.primary}} and {{colors.secondary}} phase blocks.

Budget:
  - Spend to date.
  - Budget remaining.
  - Variance analysis.
  - Forecast to completion.
  - Charts: {{colors.primary}} actuals, {{colors.accent}} forecast.

Risks and issues:
  - Open risks.
  - Active issues.
  - Mitigation status.
  - New items.
  - Risk cards: Severity-colored left border.

Next period:
  - Planned activities.
  - Key decisions needed.
  - Client action items.
  - Meeting schedule.
  - Action items: Checkbox style with {{colors.primary}} checks.

[FORMATS]
Full report: Weekly/bi-weekly detail.
Summary: Executive brief (1 page).
Dashboard: Visual metrics only using {{grid_systems.dashboard_grid}}.

[SPECIFICATIONS]
Frequency: Weekly or as agreed.
Distribution: Agreed stakeholders.
Format: Word, PDF, or slides.
Typography: {{typography.heading_font}} for sections.

[GRID & FRAME]
Grid system: {{grid_systems.dashboard_grid.description}}
Metric cards: {{grid_systems.dashboard_grid.cell_radius}} corners
Frame style: {{frame_styles.solid.token}}
Card spacing: {{spacing.gap_md}}

Quarterly Business Review¶

# DESIGN SYSTEM INTEGRATION
variant: "creative_clay"  # Distinctive, memorable for relationship milestones
grid_system: "editorial_grid"
frame_style: "frame_solid"
alternatives: ["trusted_advisor", "bold_challenger"]

[ASSET: TEMPLATE - QBR]
Quarterly client relationship review.
Variant: creative_clay for distinctive, memorable presentations.

[PRESENTATION STRUCTURE]
Executive summary:
  - Relationship overview.
  - Quarter highlights.
  - Key metrics.
  - Looking ahead.
  - Hero slide: {{creative_clay.special_elements.blob_shapes}} background.

Engagement summary:
  - Services delivered.
  - Projects completed.
  - Hours/resources utilized.
  - SLA performance.
  - Metrics: {{colors.primary}} with {{colors.accent}} highlights.

Results and value:
  - Outcomes achieved.
  - ROI demonstration.
  - Success stories.
  - Client testimonials.
  - Quote blocks: {{frame_styles.double.token}} accent border.

Service performance:
  - SLA metrics.
  - Ticket analysis.
  - Response times.
  - Resolution rates.
  - Dashboard: {{grid_systems.dashboard_grid}} for metric cards.

Roadmap:
  - Upcoming initiatives.
  - Recommendations.
  - Industry trends.
  - Technology updates.
  - Timeline: {{colors.primary}} to {{colors.accent}} gradient path.

Strategic discussion:
  - Client priorities.
  - Alignment opportunities.
  - Expansion possibilities.
  - Partnership evolution.
  - Discussion slide: Alternating {{creative_clay.special_elements.section_alternation.pattern}}.

[SPECIFICATIONS]
Format: PowerPoint presentation.
Length: 15-25 slides.
Delivery: In-person or video.
Follow-up: Summary email with materials.
Typography: {{creative_clay.typography.display_size}} headings.
Corners: {{creative_clay.visual.border_radius}}.

[GRID & FRAME]
Grid system: {{grid_systems.editorial_grid.description}}
Column rules: {{grid_systems.editorial_grid.column_rules}}
Frame style: {{frame_styles.solid.token}}
Section contrast: {{creative_clay.composition.section_contrast}}
Blob backgrounds: {{creative_clay.special_elements.blob_shapes.colors}}

Financial Templates¶

Invoice Template¶

# DESIGN SYSTEM INTEGRATION
variant: "clean_developer"  # Precision and clarity for financial documents
grid_system: "structured_grid"
frame_style: "frame_solid"
alternatives: ["trusted_advisor"]

[ASSET: TEMPLATE - INVOICE]
Standard billing invoice.
Variant: clean_developer for precise, unambiguous financial clarity.

[DOCUMENT STRUCTURE]
Header:
  - SBK logo and legal name.
  - Invoice number.
  - Invoice date.
  - Due date.
  - PO number (if applicable).
  - Header area: {{colors.background}} with {{colors.primary}} accent line.

Addresses:
  - Bill to (client billing).
  - Remit to (SBK payment).
  - Address blocks: {{frame_styles.solid.token}} at {{grid_systems.structured_grid.outer_opacity}}.

Invoice body:
  - Line items.
  - Description.
  - Quantity/hours.
  - Rate.
  - Amount.
  - Subtotal.
  - Taxes (if applicable).
  - Total due.
  - Table: {{grid_systems.structured_grid}} with alternating row {{colors.surface}}.
  - Currency values: {{typography.code_font}} for numerical precision.
  - Total row: {{colors.primary}} text, {{typography.heading_weight}}.

Footer:
  - Payment terms.
  - Payment methods.
  - Late payment terms.
  - Contact for questions.
  - Footer: {{colors.text_secondary}} text on {{colors.background}}.

[VARIATIONS]
Time and materials: Hourly detail with date column.
Fixed fee: Milestone payments with completion %.
Retainer: Monthly recurring with period indicator.
Expense: Reimbursable expenses with receipt refs.

[SPECIFICATIONS]
Format: PDF (generated from system).
Numbering: Sequential, year-prefixed.
Currency: As per contract.
Terms: Net 30 standard.
Typography: {{typography.code_font}} for amounts, {{typography.body_font}} for text.

[GRID & FRAME]
Grid system: {{grid_systems.structured_grid.description}}
Frame style: {{frame_styles.solid.token}}
Table borders: {{visual.border_width}} {{colors.border}}
Header row: {{colors.surface}} background
Totals: {{colors.primary}} underline

Budget Template¶

# DESIGN SYSTEM INTEGRATION
variant: "clean_developer"  # Precision for financial planning
grid_system: "structured_grid"
frame_style: "frame_solid"
alternatives: ["trusted_advisor"]

[ASSET: TEMPLATE - BUDGET]
Project or engagement budget.
Variant: clean_developer for precise financial tracking.

[STRUCTURE]
Summary:
  - Total budget.
  - Budget by category.
  - Budget by phase.
  - Contingency.
  - Summary cards: {{grid_systems.dashboard_grid.cell_radius}} corners.
  - Total highlight: {{colors.primary}} accent.

Labor:
  - Role/resource.
  - Hours.
  - Rate.
  - Total.
  - Rate column: {{typography.code_font}}.

Materials/licenses:
  - Item.
  - Quantity.
  - Unit cost.
  - Total.

Travel/expenses:
  - Category.
  - Estimate.
  - Per-trip or total.

Third party:
  - Vendor/contractor.
  - Service.
  - Cost.

Contingency:
  - Percentage.
  - Amount.
  - Trigger criteria.
  - Callout: {{colors.warning}} indicator for contingency use.

[TRACKING]
Actuals: Monthly update.
Variance: Planned vs. actual.
  - Under budget: {{colors.success}}
  - Over budget: {{colors.error}}
  - On track: {{colors.text_primary}}
Forecast: Estimate at completion.

[GRID & FRAME]
Grid system: {{grid_systems.structured_grid.description}}
Frame style: {{frame_styles.solid.token}}
Table headers: {{colors.surface}} background
Currency columns: Right-aligned, {{typography.code_font}}
Variance indicators: Color-coded per status

Operational Templates¶

Meeting Agenda¶

[ASSET: TEMPLATE - AGENDA]
Standard meeting agenda.

[STRUCTURE]
Header:
  - Meeting title.
  - Date and time.
  - Location/conference link.
  - Attendees.

Agenda items:
  - Item number.
  - Topic.
  - Owner.
  - Time allocation.
  - Objective (inform/discuss/decide).

Pre-read:
  - Required materials.
  - Links to documents.

Notes section:
  - Space for in-meeting notes.
  - Action items capture.
  - Decisions made.

[VARIATIONS]
Internal: Team meetings.
Client: Client-facing meetings.
Workshop: Collaborative sessions.
Review: Decision meetings.

[SPECIFICATIONS]
Format: Word, Google Doc.
Distribution: 24-48 hours before.
Follow-up: Notes within 24 hours.

Meeting Notes¶

[ASSET: TEMPLATE - NOTES]
Meeting documentation.

[STRUCTURE]
Header:
  - Meeting title.
  - Date and time.
  - Attendees (present/absent).
  - Scribe.

Discussion summary:
  - Topic.
  - Key points.
  - Decisions made.

Action items:
  - Item number.
  - Action description.
  - Owner.
  - Due date.
  - Status.

Next meeting:
  - Date/time.
  - Proposed agenda.

Attachments:
  - Related documents.
  - Reference links.

[SPECIFICATIONS]
Distribution: Within 24 hours.
Format: Email or shared doc.
Storage: Project documentation.

Project Charter¶

[ASSET: TEMPLATE - CHARTER]
Project initiation document.

[STRUCTURE]
Project overview:
  - Project name.
  - Project manager.
  - Sponsor.
  - Start/end dates.

Business case:
  - Problem statement.
  - Opportunity.
  - Expected benefits.
  - Success criteria.

Scope:
  - In scope.
  - Out of scope.
  - Key deliverables.
  - Constraints.

Stakeholders:
  - Stakeholder.
  - Role.
  - Interest level.
  - Communication needs.

Resources:
  - Team members.
  - Budget summary.
  - Tools/systems.
  - External dependencies.

Risks:
  - Initial risk assessment.
  - Key assumptions.

Governance:
  - Decision authority.
  - Escalation path.
  - Status reporting.

Approvals:
  - Signature blocks.
  - Approval date.

[SPECIFICATIONS]
Format: Word document.
Length: 2-5 pages.
Approval: Required before kickoff.

Communication Templates¶

Email Templates¶

# DESIGN SYSTEM INTEGRATION
variant: "modern_partner"  # Approachable warmth for communications
grid_system: "minimal_grid"
frame_style: "frame_solid"
alternatives: ["trusted_advisor"]

[ASSET: TEMPLATE - EMAILS]
Standard email communications.
Variant: modern_partner for approachable, collaborative tone.

[TEMPLATE CATEGORIES]
Prospecting:
  - Initial outreach.
  - Follow-up sequences.
  - Meeting request.
  - Value proposition.

Sales:
  - Proposal submission.
  - Proposal follow-up.
  - Contract submission.
  - Win confirmation.

Project:
  - Kickoff announcement.
  - Status update.
  - Milestone completion.
  - Issue escalation.

Client service:
  - Welcome/onboarding.
  - Check-in.
  - Renewal discussion.
  - Feedback request.

Internal:
  - Announcement.
  - Request.
  - Status update.
  - Recognition.

[EMAIL STRUCTURE]
Subject: Clear, actionable.
Greeting: Appropriate formality.
Opening: Context/purpose.
Body: Key content.
Call to action: Clear next step with {{colors.accent}} button.
Closing: Professional sign-off.
Signature: Standard format.

[HTML EMAIL STYLING]
Header logo: Brand logo on {{colors.background}}.
Body background: {{colors.surface}}.
Text: {{colors.text_primary}}, {{typography.body_font}}.
Links: {{colors.primary}}.
CTA button: {{colors.accent}} with {{colors.text_inverse}} text.
Footer: {{colors.text_secondary}} on {{colors.background}}.
Border radius: {{visual.border_radius}}.

[SPECIFICATIONS]
Tone: Professional, warm.
Length: Concise (scannable).
Format: Plain text or light HTML.
Mobile: Readable on mobile.
Max width: 600px for email clients.

Letter Templates¶

[ASSET: TEMPLATE - LETTERS]
Formal business correspondence.

[TEMPLATE TYPES]
Engagement letter:
  - Terms of engagement.
  - Scope summary.
  - Responsibilities.
  - Next steps.

Thank you letter:
  - Meeting follow-up.
  - Proposal thank you.
  - Project completion.
  - Referral appreciation.

Reference letter:
  - Employee reference.
  - Vendor reference.
  - Client testimonial.

Notification letter:
  - Policy changes.
  - Rate changes.
  - Personnel changes.
  - Service updates.

[LETTER FORMAT]
Letterhead: SBK branded.
Date: Full date format.
Recipient: Name, title, address.
Salutation: Dear Mr./Ms./Dr.
Body: Clear paragraphs.
Closing: Sincerely, Regards.
Signature: Handwritten + printed.
Enclosures: If applicable.

[SPECIFICATIONS]
Format: Word and PDF.
Paper: Quality letterhead stock.
Mailing: Matching envelope.

Form Templates¶

Client Intake Form¶

[ASSET: TEMPLATE - INTAKE FORM]
New client/project information gathering.

[SECTIONS]
Company information:
  - Legal name.
  - DBA (if applicable).
  - Address.
  - Website.
  - Industry.
  - Company size.

Contact information:
  - Primary contact.
  - Billing contact.
  - Technical contact.
  - Executive sponsor.

Project information:
  - Project name/description.
  - Objectives.
  - Timeline requirements.
  - Budget range.

Technical information:
  - Current environment.
  - Key systems.
  - Integrations.
  - Constraints.

Administrative:
  - Preferred communication.
  - Meeting availability.
  - Document sharing preference.
  - Special requirements.

[SPECIFICATIONS]
Format: Online form or PDF fillable.
Data: Feeds into CRM/PM systems.
Privacy: Confidentiality notice.

Feedback Form¶

[ASSET: TEMPLATE - FEEDBACK FORM]
Client and project feedback collection.

[QUESTION AREAS]
Overall satisfaction:
  - Project satisfaction (1-10).
  - Team satisfaction (1-10).
  - Communication (1-10).
  - Value (1-10).

Specific feedback:
  - What went well?
  - What could improve?
  - Recommendations for others?

Future engagement:
  - Likelihood to continue.
  - Likelihood to refer.
  - Interest in other services.

Open comments:
  - Additional feedback.
  - Testimonial permission.

[SPECIFICATIONS]
Format: Online survey.
Timing: Post-project and periodic.
Anonymous option: Depending on need.
Follow-up: Thank you and action.

Framework Components¶

Reusable Content Blocks¶

[ASSET: TEMPLATE - CONTENT BLOCKS]
Modular content for assembly.

[BLOCK TYPES]
Company overview:
  - Standard: 100 words.
  - Extended: 300 words.
  - Elevator: 50 words.

Service descriptions:
  - Each service pillar.
  - Various lengths.
  - Technical/executive versions.

Team bios:
  - Standard format.
  - Various lengths.
  - Role-appropriate content.

Case study summaries:
  - Challenge.
  - Solution.
  - Results.
  - Quote.

Differentiators:
  - Key differentiators.
  - Proof points.
  - Comparisons.

Legal/boilerplate:
  - Confidentiality notices.
  - Terms references.
  - Disclaimers.

[MANAGEMENT]
Storage: Central content library.
Versions: Track updates.
Approval: Maintain approved versions.
Usage: Copy, don't modify source.

Style Framework¶

# DESIGN SYSTEM INTEGRATION
# This framework maps to the parameterized design system tokens
parent_config: "./readme.md"
schema_version: "2.0"

[ASSET: TEMPLATE - STYLE FRAMEWORK]
Consistent styling across templates via parameterized tokens.

[TYPOGRAPHY]
Headings: {{typography.heading_font}}, {{typography.heading_weight}}.
Body: {{typography.body_font}}, {{typography.text_base}}.
Emphasis: {{typography.weight_semibold}}, not italic.
Lists: Consistent bullet/number style.
Tracking: {{typography.heading_tracking}} for headings, {{typography.body_tracking}} for body.
Line height: {{typography.leading_normal}} for body text.

[COLORS - Variant Dependent]
Primary: {{colors.primary}} for headings/accents.
Secondary: {{colors.secondary}} for supporting elements.
Accent: {{colors.accent}} for highlights and CTAs.
Text: {{colors.text_primary}} for body, {{colors.text_secondary}} for captions.
Background: {{colors.background}} (variant-specific).
Surface: {{colors.surface}} for cards and elevated elements.
Border: {{colors.border}} for dividers and table lines.

[SPACING]
Margins: {{spacing.page_margin}} standard.
Paragraph: {{spacing.paragraph_gap}} after, not indent.
Sections: {{spacing.section_gap}} between major sections.
Tables: {{spacing.space_3}} cell padding.

[ELEMENTS]
Headers: Logo, page numbers. Height: {{spacing.header_height}}.
Footers: Confidentiality, dates. Height: {{spacing.footer_height}}.
Tables: {{frame_styles.solid.token}} at {{grid_systems.structured_grid.inner_opacity}}.
Charts: {{colors.primary}}, {{colors.secondary}}, {{colors.accent}} palette.
Images: {{visual.border_radius}} corners, {{visual.shadow}} on elevated.

[GRID SYSTEMS - Available Options]
minimal_grid: {{grid_systems.minimal_grid.description}}
subtle_grid: {{grid_systems.subtle_grid.description}}
structured_grid: {{grid_systems.structured_grid.description}}
technical_grid: {{grid_systems.technical_grid.description}}
editorial_grid: {{grid_systems.editorial_grid.description}}
dashboard_grid: {{grid_systems.dashboard_grid.description}}
cyber_grid: {{grid_systems.cyber_grid.description}}

[FRAME STYLES - Available Options]
solid: {{frame_styles.solid.description}}
dotted: {{frame_styles.dotted.description}}
dashed: {{frame_styles.dashed.description}}
double: {{frame_styles.double.description}}
gradient: {{frame_styles.gradient.description}}
glow: {{frame_styles.glow.description}}

Production Guidelines¶

Template Management¶

template_governance:
  storage:
    location: "Central template library"
    access: "Role-based permissions"
    backup: "Regular automated backup"

  versioning:
    naming: "template-name-vX.Y"
    tracking: "Change log maintained"
    approval: "Required for major changes"
    schema_version: "2.0"  # Parameterized design system version

  distribution:
    method: "Pull from library (not email)"
    training: "Usage guidelines provided"
    support: "Template owner identified"

  maintenance:
    review: "Quarterly review cycle"
    updates: "Coordinated rollout"
    retirement: "Archived, not deleted"

  # Design system integration
  design_system_config:
    parent_reference: "./readme.md"
    token_inheritance: true
    variant_switching: true
    grid_system_support:
      - "minimal_grid"
      - "subtle_grid"
      - "structured_grid"
      - "technical_grid"
      - "editorial_grid"
      - "dashboard_grid"
      - "cyber_grid"
    frame_style_support:
      - "solid"
      - "dotted"
      - "dashed"
      - "double"
      - "gradient"
      - "glow"

Template Creation Process¶

creation_process:
  request:
    - "Identify need and use case"
    - "Check for existing templates"
    - "Define requirements"
    - "Obtain approval to create"

  development:
    - "Draft structure and content"
    - "Apply brand guidelines"
    - "Build in flexibility"
    - "Create instructions"

  review:
    - "Brand compliance check"
    - "Content accuracy review"
    - "Usability testing"
    - "Legal review if needed"

  deployment:
    - "Add to template library"
    - "Create user documentation"
    - "Announce availability"
    - "Train users if needed"

Quality Checklist¶

Before finalizing any template:

Brand & Design System Alignment¶

Follows brand guidelines
Uses appropriate design system variant (trusted_advisor, bold_challenger, etc.)
Token placeholders properly resolved ({{colors.primary}}, {{typography.heading_font}}, etc.)
Grid system appropriate for content type (structured_grid for data, minimal_grid for letters)
Frame style consistent with variant (frame_glow for cyber_shield, frame_solid for trusted_advisor)

Structure & Usability¶

Governance¶

Version controlled (schema_version: 2.0)
Approved for distribution
Training/documentation ready
Maintenance owner assigned

Blueprint Technical Specific (if applicable)¶

CAD annotation styles properly applied
Dimension lines and leader callouts formatted
Section markers (A-1, B-2) positioned correctly
Technical grid overlay visible at appropriate opacity
Monospace font used for specifications and dimensions

Design System Variant Quick Reference¶

# VARIANT SELECTION GUIDE FOR TEMPLATES

variant_quick_reference:
  trusted_advisor:
    description: "Corporate blue, conservative - Professional stability"
    colors: "#2563eb (blue), #0f172a (navy)"
    best_for: ["SOWs", "contracts", "executive summaries", "compliance docs"]
    grid: "subtle_grid"
    frame: "frame_solid"

  modern_partner:
    description: "Teal/cyan, collaborative - Partnership warmth"
    colors: "#0d9488 (teal), #06b6d4 (cyan)"
    best_for: ["status reports", "meeting notes", "collaborative docs"]
    grid: "minimal_grid"
    frame: "frame_solid"

  bold_challenger:
    description: "High contrast, bold - Confident differentiation"
    colors: "#0f172a (charcoal), #ea580c (orange)"
    best_for: ["executive proposals", "competitive responses", "pitch decks"]
    grid: "structured_grid"
    frame: "frame_solid"

  cyber_shield:
    description: "Deep navy + electric blue - CrowdStrike-inspired security"
    colors: "#0a0a0b (black), #dc2626 (red)"
    best_for: ["security assessments", "threat reports", "incident docs"]
    grid: "cyber_grid"
    frame: "frame_glow"
    mode: "dark"

  sentinel_guard:
    description: "Purple/magenta + AI neural patterns - SentinelOne-inspired"
    colors: "#9333ea (purple), #d946ef (fuchsia)"
    best_for: ["AI/ML security", "autonomous protection", "advanced defense"]
    grid: "dashboard_grid"
    frame: "frame_gradient"
    mode: "dark"

  clean_developer:
    description: "Ultra-clean, purple accent - Stripe-inspired clarity"
    colors: "#4f46e5 (indigo), #7c3aed (violet)"
    best_for: ["invoices", "budgets", "technical documentation", "API docs"]
    grid: "minimal_grid"
    frame: "frame_solid"
    mode: "light"

  creative_clay:
    description: "Warm cream + coral/terracotta - Clay-inspired uniqueness"
    colors: "#0f172a (charcoal), #f97316 (orange), #f59e0b (amber)"
    best_for: ["QBRs", "annual reports", "brand presentations"]
    grid: "editorial_grid"
    frame: "frame_solid"
    special: "blob shapes, gradient text, section alternation"

  blueprint_technical:
    description: "#1C1C1C + #F05023 - AlignUI-inspired engineering drawing aesthetic"
    colors: "#1C1C1C (charcoal), #F05023 (engineering orange)"
    best_for: ["technical proposals", "engineering specs", "architecture docs", "CAD annotations"]
    grid: "technical_grid"
    frame: "frame_dashed"
    special: "dimension lines, leader callouts, section markers, revision clouds"

Last Updated: February 2026 Version: 2.0 (Parameterized Design System Integration)