type: user

role: user

content:
Save the following memories to /Users/russgoerend/.claude/projects/-Users-russgoerend-Desktop-Portfolio-HTMLs/memory/. For each memory, write the file first, then update MEMORY.md.

---

MEMORY 1 — file: project_apex_portfolio.md
---
name: project-apex-portfolio
description: Overview of the Waukee APEX portfolio system — what files exist, how they connect, and the design system in use
metadata:
  type: project
---

The Portfolio HTMLs folder is a standalone, offline HTML/CSS/JS system for Waukee APEX student-associates. No build tools, no backend — everything runs in the browser with localStorage for persistence.

**Key files:**
- `APEX_Professional_Dashboard.html` — central hub linking to all other tools
- `APEX_Professional_Portfolio.html` — portfolio evidence tracker
- `APEX_Review_Prep.html` — performance review preparation tool
- `Standard1.html` through `Standard5.html` — one page per APEX standard
- `Video Production Playbook.html`, `Social Media Playbook.html`, `Marketing Analytics Playbook.html` — project workflow guides
- `Project Task Boards.html` — standalone task board
- `APEX Vertical.png` — logo used in nav across all pages

**Design system:** Purple `#500778` primary, lime `#c4d600` secondary/accent. Inter font. All pages share the same fixed top nav (logo + links), white card components, and purple/gold color language.

**Why:** Built for Russ Goerend's DCS (Designing Communication Solutions) class at Waukee APEX. Student-associates use it throughout the semester to document work, track standards, and prepare for performance reviews.

**How to apply:** When editing any file, match the existing design system. All files are self-contained — edits are local only. No git repo.

---

MEMORY 2 — file: project_playbook_pattern.md
---
name: project-playbook-pattern
description: The playbook sidebar UI pattern used across Video, Social Media, and Marketing Analytics playbooks
metadata:
  type: project
---

All three playbooks (and Standard3 after a redesign) use the same sidebar UI pattern:

**Sidebar structure:** White background, `border-right: 1px solid #E5E7EB`, `position: sticky`, `top: var(--nav-height)`, `height: calc(100vh - var(--nav-height))`. Contains: sidebar-header (title + project manager + progress bar), phase groups with phase labels, step-btn buttons with step-check circles, sidebar-footer.

**Project switcher:** Each playbook stores multiple projects in localStorage under a namespaced key (e.g. `apex_dcs_video_projects_v1`). Functions: `newProject()` (prompts for name), `duplicateProject()` (prompts for name), `renameProject()`, `deleteProject()` (blocked if only one project). Save-before-switch bug was fixed — all switching functions call `saveState()` first.

**Step completion:** `.step-btn.done` adds a green checkmark to the `.step-check` circle. Progress bar fills via `updateProgress()`.

**Callout/teaching CSS classes:** `.callout`, `.callout-yellow`, `.callout-blue`, `.callout-green`, `.callout-purple`, `.glossary-term`, `.how-to-list` (numbered), `.platform-grid` (Social Media only).

**Why:** Pattern was built so student-associates can run multiple concurrent projects of the same type (e.g. two video projects) without duplicating files.

**How to apply:** If adding a new playbook or standard page, use this sidebar structure. The Marketing Analytics and Social Media playbooks are good reference implementations.

---

MEMORY 3 — file: project_foundational_content.md
---
name: project-foundational-content
description: Foundational "Before You Start" orientation pattern added to Marketing Analytics and Social Media playbooks
metadata:
  type: project
---

Both Marketing Analytics and Social Media playbooks have a Phase 0 "Before You Start" step added as the first step. Pattern established because students enter with zero prerequisite knowledge.

**What Phase 0 includes:**
- Plain-English explanation of what the discipline actually is in a professional context
- Glossary of 8–10 key terms with definitions written for zero-knowledge students
- Tool overview (what each tool is for, not just its name)
- Callout normalizing that they won't have access to everything
- Description of what a finished project looks like

**Marketing Analytics Phase 0 also added:**
- Expanded Metrics Plan step: plain-English definitions of CTR, CPC, CPA, ROAS, Bounce Rate; "pick your north-star metric" callout; Inputs→Outputs→Outcomes framework expanded
- Expanded Analysis step: reporting-vs-analysis callout with side-by-side example; numbered how-to guide for actually doing the analysis

**Social Media Phase 0 also added:**
- Expanded Content Creation: platform format guide (dimensions/lengths), caption writing framework, hashtag strategy
- Expanded Publishing: posting time guidelines + first-hour playbook
- Performance Review checkpoint: "What to Measure" card defining Reach, Engagement Rate, Top Post, Follower Growth, Story Completion, Link Clicks
- Fixed bug: `.callout-yellow` and `.callout-blue` were used in HTML but not defined in CSS

**How to apply:** If adding a new playbook (e.g. a fourth strand), lead with Phase 0 using this pattern. The Video Production Playbook predates this pattern and does not have Phase 0 — it could be added later.

---

Now update MEMORY.md to add entries for all three. Read MEMORY.md first to see what's already there, then append the new entries.

userType: external

entrypoint: claude-vscode

gitBranch: HEAD


content:
- update-config: Use this skill to configure the Claude Code harness via settings.json. Automated behaviors ("from now on when X", "each time X", "whenever X", "before/after X") require hooks configured in settings.json - the harness executes these, not Claude, so memory/preferences cannot fulfill them. Also use for: permissions ("allow X", "add permission", "move permission to"), env vars ("set X=Y"), hook troubleshooting, or any changes to settings.json/settings.local.json files. Examples: "allow npm commands", "add bq permission to global settings", "move permission to user settings", "set DEBUG=true", "when claude stops show X". For simple settings like theme/model, suggest the /config command.
- keybindings-help: Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify ~/.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
- simplify: Review changed code for reuse, quality, and efficiency, then fix any issues found.
- fewer-permission-prompts: Scan your transcripts for common read-only Bash and MCP tool calls, then add a prioritized allowlist to project .claude/settings.json to reduce permission prompts.
- loop: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo). Omit the interval to let the model self-pace. - When the user wants to set up a recurring task, poll for status, or run something repeatedly on an interval (e.g. "check the deploy every 5 minutes", "keep running /babysit-prs"). Do NOT invoke for one-off tasks.
- schedule: Create, update, list, or run scheduled remote agents (routines) that execute on a cron schedule. - When the user wants to schedule a recurring remote agent, set up automated tasks, create a cron job for Claude Code, or manage their scheduled agents/routines. Also use when the user wants a one-time scheduled run ("run this once at 3pm", "remind me to check X tomorrow").
- claude-api: Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements).
TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a Claude feature (caching, thinking, compaction, tool use, batch, files, citations, memory) or model (Opus/Sonnet/Haiku) in a file; questions about prompt caching / cache hit rate in an Anthropic SDK project.
SKIP: file imports `openai`/other-provider SDK, filename like `*-openai.py`/`*-generic.py`, provider-neutral code, general programming/ML.
- init: Initialize a new CLAUDE.md file with codebase documentation
- review: Review a pull request
- security-review: Complete a security review of the pending changes on the current branch

type: attachment


type: message

role: assistant

type: text

text: I'll save all three memory files and update MEMORY.md. Let me start by reading the existing MEMORY.md and checking the memory directory.

service_tier: standard

attributionAgent: general-purpose

type: assistant


Bash

command: ls /Users/russgoerend/.claude/projects/-Users-russgoerend-Desktop-Portfolio-HTMLs/memory/ 2>/dev/null && echo "---DIR EXISTS---" || echo "---DIR MISSING---"

description: Check if memory directory exists

type: direct

speed: standard


content: ---DIR EXISTS---


toolUseResult: Error: File does not exist. Note: your current working directory is /Users/russgoerend/Desktop/Portfolio HTMLs.


description: List files in memory directory


content: (Bash completed with no output)


text: The directory exists but is empty. I'll write all three memory files and create MEMORY.md fresh.


Write

content:
---
name: project-apex-portfolio
description: Overview of the Waukee APEX portfolio system — what files exist, how they connect, and the design system in use
metadata:
  type: project
---

The Portfolio HTMLs folder is a standalone, offline HTML/CSS/JS system for Waukee APEX student-associates. No build tools, no backend — everything runs in the browser with localStorage for persistence.

**Key files:**
- `APEX_Professional_Dashboard.html` — central hub linking to all other tools
- `APEX_Professional_Portfolio.html` — portfolio evidence tracker
- `APEX_Review_Prep.html` — performance review preparation tool
- `Standard1.html` through `Standard5.html` — one page per APEX standard
- `Video Production Playbook.html`, `Social Media Playbook.html`, `Marketing Analytics Playbook.html` — project workflow guides
- `Project Task Boards.html` — standalone task board
- `APEX Vertical.png` — logo used in nav across all pages

**Design system:** Purple `#500778` primary, lime `#c4d600` secondary/accent. Inter font. All pages share the same fixed top nav (logo + links), white card components, and purple/gold color language.

**Why:** Built for Russ Goerend's DCS (Designing Communication Solutions) class at Waukee APEX. Student-associates use it throughout the semester to document work, track standards, and prepare for performance reviews.

**How to apply:** When editing any file, match the existing design system. All files are self-contained — edits are local only. No git repo.


content: File created successfully at: /Users/russgoerend/.claude/projects/-Users-russgoerend-Desktop-Portfolio-HTMLs/memory/project_apex_portfolio.md (file state is current in your context — no need to Read it back)


content:
---
name: project-playbook-pattern
description: The playbook sidebar UI pattern used across Video, Social Media, and Marketing Analytics playbooks
metadata:
  type: project
---

All three playbooks (and Standard3 after a redesign) use the same sidebar UI pattern:

**Sidebar structure:** White background, `border-right: 1px solid #E5E7EB`, `position: sticky`, `top: var(--nav-height)`, `height: calc(100vh - var(--nav-height))`. Contains: sidebar-header (title + project manager + progress bar), phase groups with phase labels, step-btn buttons with step-check circles, sidebar-footer.

**Project switcher:** Each playbook stores multiple projects in localStorage under a namespaced key (e.g. `apex_dcs_video_projects_v1`). Functions: `newProject()` (prompts for name), `duplicateProject()` (prompts for name), `renameProject()`, `deleteProject()` (blocked if only one project). Save-before-switch bug was fixed — all switching functions call `saveState()` first.

**Step completion:** `.step-btn.done` adds a green checkmark to the `.step-check` circle. Progress bar fills via `updateProgress()`.

**Callout/teaching CSS classes:** `.callout`, `.callout-yellow`, `.callout-blue`, `.callout-green`, `.callout-purple`, `.glossary-term`, `.how-to-list` (numbered), `.platform-grid` (Social Media only).

**Why:** Pattern was built so student-associates can run multiple concurrent projects of the same type (e.g. two video projects) without duplicating files.

**How to apply:** If adding a new playbook or standard page, use this sidebar structure. The Marketing Analytics and Social Media playbooks are good reference implementations.


content: File created successfully at: /Users/russgoerend/.claude/projects/-Users-russgoerend-Desktop-Portfolio-HTMLs/memory/project_playbook_pattern.md (file state is current in your context — no need to Read it back)


content:
---
name: project-foundational-content
description: Foundational "Before You Start" orientation pattern added to Marketing Analytics and Social Media playbooks
metadata:
  type: project
---

Both Marketing Analytics and Social Media playbooks have a Phase 0 "Before You Start" step added as the first step. Pattern established because students enter with zero prerequisite knowledge.

**What Phase 0 includes:**
- Plain-English explanation of what the discipline actually is in a professional context
- Glossary of 8–10 key terms with definitions written for zero-knowledge students
- Tool overview (what each tool is for, not just its name)
- Callout normalizing that they won't have access to everything
- Description of what a finished project looks like

**Marketing Analytics Phase 0 also added:**
- Expanded Metrics Plan step: plain-English definitions of CTR, CPC, CPA, ROAS, Bounce Rate; "pick your north-star metric" callout; Inputs→Outputs→Outcomes framework expanded
- Expanded Analysis step: reporting-vs-analysis callout with side-by-side example; numbered how-to guide for actually doing the analysis

**Social Media Phase 0 also added:**
- Expanded Content Creation: platform format guide (dimensions/lengths), caption writing framework, hashtag strategy
- Expanded Publishing: posting time guidelines + first-hour playbook
- Performance Review checkpoint: "What to Measure" card defining Reach, Engagement Rate, Top Post, Follower Growth, Story Completion, Link Clicks
- Fixed bug: `.callout-yellow` and `.callout-blue` were used in HTML but not defined in CSS

**How to apply:** If adding a new playbook (e.g. a fourth strand), lead with Phase 0 using this pattern. The Video Production Playbook predates this pattern and does not have Phase 0 — it could be added later.


content: File created successfully at: /Users/russgoerend/.claude/projects/-Users-russgoerend-Desktop-Portfolio-HTMLs/memory/project_foundational_content.md (file state is current in your context — no need to Read it back)


text: Now I'll create MEMORY.md with entries for all three.


content:
# Project Memory

This file indexes all saved memories for the Portfolio HTMLs project.

---

## project-apex-portfolio
**File:** `project_apex_portfolio.md`
**Description:** Overview of the Waukee APEX portfolio system — what files exist, how they connect, and the design system in use
**Type:** project
**Summary:** Standalone offline HTML/CSS/JS system for Waukee APEX student-associates. Key files listed. Design system: purple `#500778` + lime `#c4d600`, Inter font, fixed top nav, white cards. Built for Russ Goerend's DCS class. No git repo, no build tools.

---

## project-playbook-pattern
**File:** `project_playbook_pattern.md`
**Description:** The playbook sidebar UI pattern used across Video, Social Media, and Marketing Analytics playbooks
**Type:** project
**Summary:** Shared sidebar UI pattern (sticky sidebar, phase groups, step-btn/step-check, progress bar). Project switcher stores multiple projects in localStorage. Save-before-switch bug fixed. Callout CSS classes documented. Reference implementations: Marketing Analytics and Social Media playbooks.

---

## project-foundational-content
**File:** `project_foundational_content.md`
**Description:** Foundational "Before You Start" orientation pattern added to Marketing Analytics and Social Media playbooks
**Type:** project
**Summary:** Phase 0 pattern for zero-knowledge students: plain-English intro, glossary (8–10 terms), tool overview, access-limitation callout, finished-project description. Marketing Analytics expanded Metrics Plan + Analysis steps. Social Media expanded Content Creation + Publishing + added Performance Review checkpoint. Fixed missing `.callout-yellow`/`.callout-blue` CSS. Video Production Playbook predates this pattern.

---


content: File created successfully at: /Users/russgoerend/.claude/projects/-Users-russgoerend-Desktop-Portfolio-HTMLs/memory/MEMORY.md (file state is current in your context — no need to Read it back)


text:
All done. Here is what was written:

- `/Users/russgoerend/.claude/projects/-Users-russgoerend-Desktop-Portfolio-HTMLs/memory/project_apex_portfolio.md` — full system overview, key files, design system, context for Russ's DCS class
- `/Users/russgoerend/.claude/projects/-Users-russgoerend-Desktop-Portfolio-HTMLs/memory/project_playbook_pattern.md` — sidebar UI pattern, project switcher, step completion, callout CSS classes
- `/Users/russgoerend/.claude/projects/-Users-russgoerend-Desktop-Portfolio-HTMLs/memory/project_foundational_content.md` — Phase 0 "Before You Start" pattern, per-playbook expansions, CSS bug fix noted
- `/Users/russgoerend/.claude/projects/-Users-russgoerend-Desktop-Portfolio-HTMLs/memory/MEMORY.md` — created fresh (was empty) with an indexed entry for all three memories, including file name, description, type, and a one-line summary of each