@ngxtm/devkit 3.7.0 → 3.9.0

package/merged-commands/c4-component.md

@@ -0,0 +1,153 @@
+---
+name: c4-component
+description: Expert C4 Component-level documentation specialist. Synthesizes C4
+  Code-level documentation into Component-level architecture, defining component
+  boundaries, interfaces, and relationships. Creates component diagrams and
+  documentation. Use when synthesizing code-level documentation into logical
+  components.
+metadata:
+  model: sonnet
+---
+
+# C4 Component Level: [Component Name]
+
+## Use this skill when
+
+- Working on c4 component level: [component name] tasks or workflows
+- Needing guidance, best practices, or checklists for c4 component level: [component name]
+
+## Do not use this skill when
+
+- The task is unrelated to c4 component level: [component name]
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Overview
+
+- **Name**: [Component name]
+- **Description**: [Short description of component purpose]
+- **Type**: [Component type: Application, Service, Library, etc.]
+- **Technology**: [Primary technologies used]
+
+## Purpose
+
+[Detailed description of what this component does and what problems it solves]
+
+## Software Features
+
+- [Feature 1]: [Description]
+- [Feature 2]: [Description]
+- [Feature 3]: [Description]
+
+## Code Elements
+
+This component contains the following code-level elements:
+
+- [c4-code-file-1.md](./c4-code-file-1.md) - [Description]
+- [c4-code-file-2.md](./c4-code-file-2.md) - [Description]
+
+## Interfaces
+
+### [Interface Name]
+
+- **Protocol**: [REST/GraphQL/gRPC/Events/etc.]
+- **Description**: [What this interface provides]
+- **Operations**:
+  - `operationName(params): ReturnType` - [Description]
+
+## Dependencies
+
+### Components Used
+
+- [Component Name]: [How it's used]
+
+### External Systems
+
+- [External System]: [How it's used]
+
+## Component Diagram
+
+Use proper Mermaid C4Component syntax. Component diagrams show components **within a single container**:
+
+```mermaid
+C4Component
+    title Component Diagram for [Container Name]
+
+    Container_Boundary(container, "Container Name") {
+        Component(component1, "Component 1", "Type", "Description")
+        Component(component2, "Component 2", "Type", "Description")
+        ComponentDb(component3, "Component 3", "Database", "Description")
+    }
+    Container_Ext(externalContainer, "External Container", "Description")
+    System_Ext(externalSystem, "External System", "Description")
+
+    Rel(component1, component2, "Uses")
+    Rel(component2, component3, "Reads from and writes to")
+    Rel(component1, externalContainer, "Uses", "API")
+    Rel(component2, externalSystem, "Uses", "API")
+```
+````
+
+**Key Principles** (from [c4model.com](https://c4model.com/diagrams/component)):
+
+- Show components **within a single container** (zoom into one container)
+- Focus on **logical components** and their responsibilities
+- Show **component interfaces** (what they expose)
+- Show how components **interact** with each other
+- Include **external dependencies** (other containers, external systems)
+
+````
+
+## Master Component Index Template
+
+```markdown
+# C4 Component Level: System Overview
+
+## System Components
+
+### [Component 1]
+- **Name**: [Component name]
+- **Description**: [Short description]
+- **Documentation**: [c4-component-name-1.md](./c4-component-name-1.md)
+
+### [Component 2]
+- **Name**: [Component name]
+- **Description**: [Short description]
+- **Documentation**: [c4-component-name-2.md](./c4-component-name-2.md)
+
+## Component Relationships
+[Mermaid diagram showing all components and their relationships]
+````
+
+## Example Interactions
+
+- "Synthesize all c4-code-\*.md files into logical components"
+- "Define component boundaries for the authentication and authorization code"
+- "Create component-level documentation for the API layer"
+- "Identify component interfaces and create component diagrams"
+- "Group database access code into components and document their relationships"
+
+## Key Distinctions
+
+- **vs C4-Code agent**: Synthesizes multiple code files into components; Code agent documents individual code elements
+- **vs C4-Container agent**: Focuses on logical grouping; Container agent maps components to deployment units
+- **vs C4-Context agent**: Provides component-level detail; Context agent creates high-level system diagrams
+
+## Output Examples
+
+When synthesizing components, provide:
+
+- Clear component boundaries with rationale
+- Descriptive component names and purposes
+- Comprehensive feature lists for each component
+- Complete interface documentation with protocols and operations
+- Links to all contained c4-code-\*.md files
+- Mermaid component diagrams showing relationships
+- Master component index with all components
+- Consistent documentation format across all components

package/merged-commands/c4-container.md

@@ -0,0 +1,171 @@
+---
+name: c4-container
+description: Expert C4 Container-level documentation specialist. Synthesizes
+  Component-level documentation into Container-level architecture, mapping
+  components to deployment units, documenting container interfaces as APIs, and
+  creating container diagrams. Use when synthesizing components into deployment
+  containers and documenting system deployment architecture.
+metadata:
+  model: sonnet
+---
+
+# C4 Container Level: System Deployment
+
+## Use this skill when
+
+- Working on c4 container level: system deployment tasks or workflows
+- Needing guidance, best practices, or checklists for c4 container level: system deployment
+
+## Do not use this skill when
+
+- The task is unrelated to c4 container level: system deployment
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Containers
+
+### [Container Name]
+
+- **Name**: [Container name]
+- **Description**: [Short description of container purpose and deployment]
+- **Type**: [Web Application, API, Database, Message Queue, etc.]
+- **Technology**: [Primary technologies: Node.js, Python, PostgreSQL, Redis, etc.]
+- **Deployment**: [Docker, Kubernetes, Cloud Service, etc.]
+
+## Purpose
+
+[Detailed description of what this container does and how it's deployed]
+
+## Components
+
+This container deploys the following components:
+
+- [Component Name]: [Description]
+  - Documentation: [c4-component-name.md](./c4-component-name.md)
+
+## Interfaces
+
+### [API/Interface Name]
+
+- **Protocol**: [REST/GraphQL/gRPC/Events/etc.]
+- **Description**: [What this interface provides]
+- **Specification**: [Link to OpenAPI/Swagger/API Spec file]
+- **Endpoints**:
+  - `GET /api/resource` - [Description]
+  - `POST /api/resource` - [Description]
+
+## Dependencies
+
+### Containers Used
+
+- [Container Name]: [How it's used, communication protocol]
+
+### External Systems
+
+- [External System]: [How it's used, integration type]
+
+## Infrastructure
+
+- **Deployment Config**: [Link to Dockerfile, K8s manifest, etc.]
+- **Scaling**: [Horizontal/vertical scaling strategy]
+- **Resources**: [CPU, memory, storage requirements]
+
+## Container Diagram
+
+Use proper Mermaid C4Container syntax:
+
+```mermaid
+C4Container
+    title Container Diagram for [System Name]
+
+    Person(user, "User", "Uses the system")
+    System_Boundary(system, "System Name") {
+        Container(webApp, "Web Application", "Spring Boot, Java", "Provides web interface")
+        Container(api, "API Application", "Node.js, Express", "Provides REST API")
+        ContainerDb(database, "Database", "PostgreSQL", "Stores data")
+        Container_Queue(messageQueue, "Message Queue", "RabbitMQ", "Handles async messaging")
+    }
+    System_Ext(external, "External System", "Third-party service")
+
+    Rel(user, webApp, "Uses", "HTTPS")
+    Rel(webApp, api, "Makes API calls to", "JSON/HTTPS")
+    Rel(api, database, "Reads from and writes to", "SQL")
+    Rel(api, messageQueue, "Publishes messages to")
+    Rel(api, external, "Uses", "API")
+```
+````
+
+**Key Principles** (from [c4model.com](https://c4model.com/diagrams/container)):
+
+- Show **high-level technology choices** (this is where technology details belong)
+- Show how **responsibilities are distributed** across containers
+- Include **container types**: Applications, Databases, Message Queues, File Systems, etc.
+- Show **communication protocols** between containers
+- Include **external systems** that containers interact with
+
+````
+
+## API Specification Template
+
+For each container API, create an OpenAPI/Swagger specification:
+
+```yaml
+openapi: 3.1.0
+info:
+  title: [Container Name] API
+  description: [API description]
+  version: 1.0.0
+servers:
+  - url: https://api.example.com
+    description: Production server
+paths:
+  /api/resource:
+    get:
+      summary: [Operation summary]
+      description: [Operation description]
+      parameters:
+        - name: param1
+          in: query
+          schema:
+            type: string
+      responses:
+        '200':
+          description: [Response description]
+          content:
+            application/json:
+              schema:
+                type: object
+````
+
+## Example Interactions
+
+- "Synthesize all components into containers based on deployment definitions"
+- "Map the API components to containers and document their APIs as OpenAPI specs"
+- "Create container-level documentation for the microservices architecture"
+- "Document container interfaces as Swagger/OpenAPI specifications"
+- "Analyze Kubernetes manifests and create container documentation"
+
+## Key Distinctions
+
+- **vs C4-Component agent**: Maps components to deployment units; Component agent focuses on logical grouping
+- **vs C4-Context agent**: Provides container-level detail; Context agent creates high-level system diagrams
+- **vs C4-Code agent**: Focuses on deployment architecture; Code agent documents individual code elements
+
+## Output Examples
+
+When synthesizing containers, provide:
+
+- Clear container boundaries with deployment rationale
+- Descriptive container names and deployment characteristics
+- Complete API documentation with OpenAPI/Swagger specifications
+- Links to all contained components
+- Mermaid container diagrams showing deployment architecture
+- Links to deployment configurations (Dockerfiles, K8s manifests, etc.)
+- Infrastructure requirements and scaling considerations
+- Consistent documentation format across all containers

package/merged-commands/c4-context.md

@@ -0,0 +1,150 @@
+---
+name: c4-context
+description: Expert C4 Context-level documentation specialist. Creates
+  high-level system context diagrams, documents personas, user journeys, system
+  features, and external dependencies. Synthesizes container and component
+  documentation with system documentation to create comprehensive context-level
+  architecture. Use when creating the highest-level C4 system context
+  documentation.
+metadata:
+  model: sonnet
+---
+
+# C4 Context Level: System Context
+
+## Use this skill when
+
+- Working on c4 context level: system context tasks or workflows
+- Needing guidance, best practices, or checklists for c4 context level: system context
+
+## Do not use this skill when
+
+- The task is unrelated to c4 context level: system context
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## System Overview
+
+### Short Description
+
+[One-sentence description of what the system does]
+
+### Long Description
+
+[Detailed description of the system's purpose, capabilities, and the problems it solves]
+
+## Personas
+
+### [Persona Name]
+
+- **Type**: [Human User / Programmatic User / External System]
+- **Description**: [Who this persona is and what they need]
+- **Goals**: [What this persona wants to achieve]
+- **Key Features Used**: [List of features this persona uses]
+
+## System Features
+
+### [Feature Name]
+
+- **Description**: [What this feature does]
+- **Users**: [Which personas use this feature]
+- **User Journey**: [Link to user journey map]
+
+## User Journeys
+
+### [Feature Name] - [Persona Name] Journey
+
+1. [Step 1]: [Description]
+2. [Step 2]: [Description]
+3. [Step 3]: [Description]
+   ...
+
+### [External System] Integration Journey
+
+1. [Step 1]: [Description]
+2. [Step 2]: [Description]
+   ...
+
+## External Systems and Dependencies
+
+### [External System Name]
+
+- **Type**: [Database, API, Service, Message Queue, etc.]
+- **Description**: [What this external system provides]
+- **Integration Type**: [API, Events, File Transfer, etc.]
+- **Purpose**: [Why the system depends on this]
+
+## System Context Diagram
+
+[Mermaid diagram showing system, users, and external systems]
+
+## Related Documentation
+
+- [Container Documentation](./c4-container.md)
+- [Component Documentation](./c4-component.md)
+```
+
+## Context Diagram Template
+
+According to the [C4 model](https://c4model.com/diagrams/system-context), a System Context diagram shows the system as a box in the center, surrounded by its users and the other systems that it interacts with. The focus is on **people (actors, roles, personas) and software systems** rather than technologies, protocols, and other low-level details.
+
+Use proper Mermaid C4 syntax:
+
+```mermaid
+C4Context
+    title System Context Diagram
+
+    Person(user, "User", "Uses the system to accomplish their goals")
+    System(system, "System Name", "Provides features X, Y, and Z")
+    System_Ext(external1, "External System 1", "Provides service A")
+    System_Ext(external2, "External System 2", "Provides service B")
+    SystemDb(externalDb, "External Database", "Stores data")
+
+    Rel(user, system, "Uses")
+    Rel(system, external1, "Uses", "API")
+    Rel(system, external2, "Sends events to")
+    Rel(system, externalDb, "Reads from and writes to")
+```
+
+**Key Principles** (from [c4model.com](https://c4model.com/diagrams/system-context)):
+
+- Focus on **people and software systems**, not technologies
+- Show the **system boundary** clearly
+- Include all **users** (human and programmatic)
+- Include all **external systems** the system interacts with
+- Keep it **stakeholder-friendly** - understandable by non-technical audiences
+- Avoid showing technologies, protocols, or low-level details
+
+## Example Interactions
+
+- "Create C4 Context-level documentation for the system"
+- "Identify all personas and create user journey maps for key features"
+- "Document external systems and create a system context diagram"
+- "Analyze system documentation and create comprehensive context documentation"
+- "Map user journeys for all key features including programmatic users"
+
+## Key Distinctions
+
+- **vs C4-Container agent**: Provides high-level system view; Container agent focuses on deployment architecture
+- **vs C4-Component agent**: Focuses on system context; Component agent focuses on logical component structure
+- **vs C4-Code agent**: Provides stakeholder-friendly overview; Code agent provides technical code details
+
+## Output Examples
+
+When creating context documentation, provide:
+
+- Clear system descriptions (short and long)
+- Comprehensive persona documentation (human and programmatic)
+- Complete feature lists with descriptions
+- Detailed user journey maps for all key features
+- Complete external system and dependency documentation
+- Mermaid context diagram showing system, users, and external systems
+- Links to container and component documentation
+- Stakeholder-friendly documentation understandable by non-technical audiences
+- Consistent documentation format

package/merged-commands/canvas-design.md

@@ -0,0 +1,130 @@
+---
+name: canvas-design
+description: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
+license: Complete terms in LICENSE.txt
+---
+
+These are instructions for creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY. Output only .md files, .pdf files, and .png files.
+
+Complete this in two steps:
+1. Design Philosophy Creation (.md file)
+2. Express by creating it on a canvas (.pdf file or .png file)
+
+First, undertake this task:
+
+## DESIGN PHILOSOPHY CREATION
+
+To begin, create a VISUAL PHILOSOPHY (not layouts or templates) that will be interpreted through:
+- Form, space, color, composition
+- Images, graphics, shapes, patterns
+- Minimal text as visual accent
+
+### THE CRITICAL UNDERSTANDING
+- What is received: Some subtle input or instructions by the user that should be taken into account, but used as a foundation; it should not constrain creative freedom.
+- What is created: A design philosophy/aesthetic movement.
+- What happens next: Then, the same version receives the philosophy and EXPRESSES IT VISUALLY - creating artifacts that are 90% visual design, 10% essential text.
+
+Consider this approach:
+- Write a manifesto for an art movement
+- The next phase involves making the artwork
+
+The philosophy must emphasize: Visual expression. Spatial communication. Artistic interpretation. Minimal words.
+
+### HOW TO GENERATE A VISUAL PHILOSOPHY
+
+**Name the movement** (1-2 words): "Brutalist Joy" / "Chromatic Silence" / "Metabolist Dreams"
+
+**Articulate the philosophy** (4-6 paragraphs - concise but complete):
+
+To capture the VISUAL essence, express how the philosophy manifests through:
+- Space and form
+- Color and material
+- Scale and rhythm
+- Composition and balance
+- Visual hierarchy
+
+**CRITICAL GUIDELINES:**
+- **Avoid redundancy**: Each design aspect should be mentioned once. Avoid repeating points about color theory, spatial relationships, or typographic principles unless adding new depth.
+- **Emphasize craftsmanship REPEATEDLY**: The philosophy MUST stress multiple times that the final work should appear as though it took countless hours to create, was labored over with care, and comes from someone at the absolute top of their field. This framing is essential - repeat phrases like "meticulously crafted," "the product of deep expertise," "painstaking attention," "master-level execution."
+- **Leave creative space**: Remain specific about the aesthetic direction, but concise enough that the next Claude has room to make interpretive choices also at a extremely high level of craftmanship.
+
+The philosophy must guide the next version to express ideas VISUALLY, not through text. Information lives in design, not paragraphs.
+
+### PHILOSOPHY EXAMPLES
+
+**"Concrete Poetry"**
+Philosophy: Communication through monumental form and bold geometry.
+Visual expression: Massive color blocks, sculptural typography (huge single words, tiny labels), Brutalist spatial divisions, Polish poster energy meets Le Corbusier. Ideas expressed through visual weight and spatial tension, not explanation. Text as rare, powerful gesture - never paragraphs, only essential words integrated into the visual architecture. Every element placed with the precision of a master craftsman.
+
+**"Chromatic Language"**
+Philosophy: Color as the primary information system.
+Visual expression: Geometric precision where color zones create meaning. Typography minimal - small sans-serif labels letting chromatic fields communicate. Think Josef Albers' interaction meets data visualization. Information encoded spatially and chromatically. Words only to anchor what color already shows. The result of painstaking chromatic calibration.
+
+**"Analog Meditation"**
+Philosophy: Quiet visual contemplation through texture and breathing room.
+Visual expression: Paper grain, ink bleeds, vast negative space. Photography and illustration dominate. Typography whispered (small, restrained, serving the visual). Japanese photobook aesthetic. Images breathe across pages. Text appears sparingly - short phrases, never explanatory blocks. Each composition balanced with the care of a meditation practice.
+
+**"Organic Systems"**
+Philosophy: Natural clustering and modular growth patterns.
+Visual expression: Rounded forms, organic arrangements, color from nature through architecture. Information shown through visual diagrams, spatial relationships, iconography. Text only for key labels floating in space. The composition tells the story through expert spatial orchestration.
+
+**"Geometric Silence"**
+Philosophy: Pure order and restraint.
+Visual expression: Grid-based precision, bold photography or stark graphics, dramatic negative space. Typography precise but minimal - small essential text, large quiet zones. Swiss formalism meets Brutalist material honesty. Structure communicates, not words. Every alignment the work of countless refinements.
+
+*These are condensed examples. The actual design philosophy should be 4-6 substantial paragraphs.*
+
+### ESSENTIAL PRINCIPLES
+- **VISUAL PHILOSOPHY**: Create an aesthetic worldview to be expressed through design
+- **MINIMAL TEXT**: Always emphasize that text is sparse, essential-only, integrated as visual element - never lengthy
+- **SPATIAL EXPRESSION**: Ideas communicate through space, form, color, composition - not paragraphs
+- **ARTISTIC FREEDOM**: The next Claude interprets the philosophy visually - provide creative room
+- **PURE DESIGN**: This is about making ART OBJECTS, not documents with decoration
+- **EXPERT CRAFTSMANSHIP**: Repeatedly emphasize the final work must look meticulously crafted, labored over with care, the product of countless hours by someone at the top of their field
+
+**The design philosophy should be 4-6 paragraphs long.** Fill it with poetic design philosophy that brings together the core vision. Avoid repeating the same points. Keep the design philosophy generic without mentioning the intention of the art, as if it can be used wherever. Output the design philosophy as a .md file.
+
+---
+
+## DEDUCING THE SUBTLE REFERENCE
+
+**CRITICAL STEP**: Before creating the canvas, identify the subtle conceptual thread from the original request.
+
+**THE ESSENTIAL PRINCIPLE**:
+The topic is a **subtle, niche reference embedded within the art itself** - not always literal, always sophisticated. Someone familiar with the subject should feel it intuitively, while others simply experience a masterful abstract composition. The design philosophy provides the aesthetic language. The deduced topic provides the soul - the quiet conceptual DNA woven invisibly into form, color, and composition.
+
+This is **VERY IMPORTANT**: The reference must be refined so it enhances the work's depth without announcing itself. Think like a jazz musician quoting another song - only those who know will catch it, but everyone appreciates the music.
+
+---
+
+## CANVAS CREATION
+
+With both the philosophy and the conceptual framework established, express it on a canvas. Take a moment to gather thoughts and clear the mind. Use the design philosophy created and the instructions below to craft a masterpiece, embodying all aspects of the philosophy with expert craftsmanship.
+
+**IMPORTANT**: For any type of content, even if the user requests something for a movie/game/book, the approach should still be sophisticated. Never lose sight of the idea that this should be art, not something that's cartoony or amateur.
+
+To create museum or magazine quality work, use the design philosophy as the foundation. Create one single page, highly visual, design-forward PDF or PNG output (unless asked for more pages). Generally use repeating patterns and perfect shapes. Treat the abstract philosophical design as if it were a scientific bible, borrowing the visual language of systematic observation—dense accumulation of marks, repeated elements, or layered patterns that build meaning through patient repetition and reward sustained viewing. Add sparse, clinical typography and systematic reference markers that suggest this could be a diagram from an imaginary discipline, treating the invisible subject with the same reverence typically reserved for documenting observable phenomena. Anchor the piece with simple phrase(s) or details positioned subtly, using a limited color palette that feels intentional and cohesive. Embrace the paradox of using analytical visual language to express ideas about human experience: the result should feel like an artifact that proves something ephemeral can be studied, mapped, and understood through careful attention. This is true art. 
+
+**Text as a contextual element**: Text is always minimal and visual-first, but let context guide whether that means whisper-quiet labels or bold typographic gestures. A punk venue poster might have larger, more aggressive type than a minimalist ceramics studio identity. Most of the time, font should be thin. All use of fonts must be design-forward and prioritize visual communication. Regardless of text scale, nothing falls off the page and nothing overlaps. Every element must be contained within the canvas boundaries with proper margins. Check carefully that all text, graphics, and visual elements have breathing room and clear separation. This is non-negotiable for professional execution. **IMPORTANT: Use different fonts if writing text. Search the `./canvas-fonts` directory. Regardless of approach, sophistication is non-negotiable.**
+
+Download and use whatever fonts are needed to make this a reality. Get creative by making the typography actually part of the art itself -- if the art is abstract, bring the font onto the canvas, not typeset digitally.
+
+To push boundaries, follow design instinct/intuition while using the philosophy as a guiding principle. Embrace ultimate design freedom and choice. Push aesthetics and design to the frontier. 
+
+**CRITICAL**: To achieve human-crafted quality (not AI-generated), create work that looks like it took countless hours. Make it appear as though someone at the absolute top of their field labored over every detail with painstaking care. Ensure the composition, spacing, color choices, typography - everything screams expert-level craftsmanship. Double-check that nothing overlaps, formatting is flawless, every detail perfect. Create something that could be shown to people to prove expertise and rank as undeniably impressive.
+
+Output the final result as a single, downloadable .pdf or .png file, alongside the design philosophy used as a .md file.
+
+---
+
+## FINAL STEP
+
+**IMPORTANT**: The user ALREADY said "It isn't perfect enough. It must be pristine, a masterpiece if craftsmanship, as if it were about to be displayed in a museum."
+
+**CRITICAL**: To refine the work, avoid adding more graphics; instead refine what has been created and make it extremely crisp, respecting the design philosophy and the principles of minimalism entirely. Rather than adding a fun filter or refactoring a font, consider how to make the existing composition more cohesive with the art. If the instinct is to call a new function or draw a new shape, STOP and instead ask: "How can I make what's already here more of a piece of art?"
+
+Take a second pass. Go back to the code and refine/polish further to make this a philosophically designed masterpiece.
+
+## MULTI-PAGE OPTION
+
+To create additional pages when requested, create more creative pages along the same lines as the design philosophy but distinctly different as well. Bundle those pages in the same .pdf or many .pngs. Treat the first page as just a single page in a whole coffee table book waiting to be filled. Make the next pages unique twists and memories of the original. Have them almost tell a story in a very tasteful way. Exercise full creative freedom.