Tools

Start with the tool that matches the pressure you can name. Identity, play, image work, budgeting, and campaign memory all need different entry states, but the same rule holds: name the input, preserve the useful state, leave an artifact that can be found again.

Tools are more interesting when they participate in a loop across the site — not when they sit alone as forms. These paths are written for returning readers who want novelty through depth, not through a feature count.

Standalone browser games are not part of the catalog yet. Play routes, session logs, and local tool state are the current game-like surfaces.

For engineers, designers, authors, and peers who need to describe what they do — to a collaborator, a hiring manager, or themselves. Especially useful when recently laid off, starting a new team, or trying to articulate your work quickly without shrinking it.

• ^ profile builder Fill in fields, get a configurable card with header, badges, sections, and footer. Copy as JSON or Spw seed. Screenshot for sharing. Local-only, no account needed.
• @ character sheet builder Start from a character sheet, then translate party role, quest, and signal items into a junior engineering mentorship card.
• ^ services card A pre-configured seed card for describing services and rates. From the services page.
• ~ ask card A card for personal asks — supplies, food, bills. The same aesthetic makes a personal need feel as intentional as a professional offer, which matters when your network includes mentors, peers, and future collaborators.

Seed cards are minimal vessels — fill in, copy, screenshot, share. Templates: new year, session, wonder, services, ask. They work well when you need something that sounds polished to a hiring manager, readable to a future collaborator, and usable by a freshman still learning the vocabulary. They also make spells less abstract: each card can hold anchors, term clusters, component kinds, and settings notes.

• ^ new year card Annual threshold card — vow, bundle, relay, revisit. For the moment when time feels writable again.
• @ session card Date, scene, turn, carry, revisit. For documenting what happened at the table.
• ?[ wonder card Question, tension, material, relay, revisit. For open questions you're genuinely uncertain about.
• @ spell ingredient card Anchor, cluster, component, setting, attribute, event. For turning a strange idea into a reusable semantic recipe.

Character sheets are a low-stakes practice for professional self-description. Describing a character's abilities, background, and tools uses the same cognitive structure as writing a profile. RPG Wednesday hosts the recurring table context, and the character-sheet builder carries that grammar into mentorship-facing engineering language, internship prep, and adjacent creative roles.

• @ rpg wednesday The recurring session — character cards, local gameplay state, session logs, and the character 'l'n'd'r as a profile specimen.
• @ session log Dated event log. Use the session seed card template to document plays.
• ~ character sheet builder Build a local character sheet that maps party role, tools, quest, and world state into a publishable junior engineering mentorship card.
• ~ midjourney bench Keep style refs, omni refs, shotboards, and collaborator-aware image experiments in a route that can expand later.

For peers navigating layoffs, career transitions, and the work of articulating what you do. These tools and links are a starting point, especially when the next step is not yet a job title but a clearer story, a better term, or a route through community that does not collapse your work into one credential.