knowledge-stack
Use this skill whenever working inside any of Nick's repos (Atlas Crew, Inferno Lab, or any folder under ~/Developer/) or whenever a conversation touches Nick's cross-cutting personal or career work — job search, interviews, tax amendment, foreclosure/tenant situation, Hard Stuff drafts, brand or design work, strategic positioning. Describes where Nick's durable knowledge lives and which layer to consult for which kind of question. Trigger before reasoning from stored memory summaries about repo architecture, product decisions, active priorities, or ongoing personal/career state. Stored memory is lossy; the backlog docs and the Basic Memory vault are the real artifacts and should be consulted first.
What this skill does
# Knowledge Stack Nick's durable knowledge lives in two layers. Stored memory summaries are lossy; these are the real artifacts. Consult them before reasoning. ## The Split **Per-repo dev work** → `backlog docs` and `backlog tasks` inside each repo. - Architecture, product strategy, implementation plans, active priorities, roadmap notes. - Consistent pattern across Nick's repos under `~/Developer/`. - For CLI mechanics, see the `backlog-md` skill. **Cross-cutting personal and career** → Basic Memory vault (via the `basic-memory` MCP). - Job search pipeline, interview prep state, tax amendment, foreclosure/tenant situation, Hard Stuff drafts, brand and design work, strategic positioning. - Obsidian is an optional UI, not required. The vault is plain markdown; any editor works. **Ephemeral conversation context** → this chat. Promote to the right layer when worth keeping. ## Operational Rules 1. **Before reasoning about a specific repo**, run `backlog doc list` in that repo. Pull relevant docs with `backlog doc view <id>` before forming conclusions from stored memory. 2. **Before reasoning about cross-cutting work**, search Basic Memory (`search_notes`, then `read_note`) before reasoning from stored memory. 3. **When a chat surfaces something durable**, propose writing it to the right layer. Don't silently drop context. 4. **Don't duplicate content across layers.** If something could plausibly live in both, ask Nick which layer owns it. ## Failure Modes to Avoid - Reasoning from stored memory summaries when fresher truth exists in backlog docs or the vault — produces stale or wrong answers. - Writing to Basic Memory what belongs in a repo's backlog docs, or vice versa — produces knowledge drift across layers that compounds over time. - Treating Obsidian as required — Nick doesn't want the Electron app running. The vault is markdown files; use whatever editor or the MCP directly. - Enumerating "Nick's repos" from memory and getting it wrong — just `ls ~/Developer/` or check the current working directory.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".