Wayfinder logo

Wayfinder

Community
devton
wayfinder

Strategic orientation, codebase mapping, architectural entry point identification, and intent framing prior to grilling, research, or prototyping.

Overview

Publisherdevton
Repositoryagentic-workflow-blueprint
Skill namewayfinder
Stars
73
Forks
4
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by devton on GitHub. Read the source before you install it.

Installation

Install the Wayfinder AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/devton/agentic-workflow-blueprint/tree/main/workflows/mattpocock/wayfinder
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/devton/agentic-workflow-blueprint.git /tmp/agentic-workflow-blueprint
mkdir -p .claude/skills
cp -r /tmp/agentic-workflow-blueprint/workflows/mattpocock/wayfinder .claude/skills/wayfinder
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Wayfinder in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Wayfinder on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Wayfinder is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

agentic-workflows-blueprint.workflow.mattpocock.wayfinder

Goal

Provide a structured codebase navigation and problem space orientation protocol to map systems, data flows, and architectural constraints before deep technical design.


Scope

  • Applies to: Feature discovery, legacy codebase navigation, architecture exploration, and initial intent framing.
  • Does not cover: Direct code execution or implementation (use execution or prototyping workflows).

Triggers

  • "/wayfinder"
  • "Run wayfinder orientation"
  • "Map codebase context for feature"
  • "Orient problem space"

Inputs

  • userPrompt: Description of the feature or architectural requirement.
  • projectSlug: Short identifier for the repository (e.g. my-backend).
  • baseBranch: Default integration branch (default: main or develop).
  • techStack: Core technology stack details.
  • existingRootDoc: Main project instruction document (AGENTS.md, CLAUDE.md).

Invariants (Guardrails)

  1. UUIDv7 Standard: Always specify UUIDv7 for all primary keys and entity IDs in resource mappings.
  2. Evidence-Based Codebase Mapping: Read actual entry points, route handlers, models, and configs before framing problem scope; do NOT assume directory or system structure.
  3. Problem Space Framing: Define explicit system boundaries, affected modules, entry/exit points, and critical unknowns.
  4. Orientation Summary: Produce a clear orientation summary (wayfinder.md or conversation context) to anchor subsequent grilling, modeling, or research phases.

Procedure

1) Parse Intent & Target Surface
  1. Analyze user prompt to identify target domain, operational context, and core goals.
  2. Extract implicit assumptions and map primary entry channels (HTTP controllers, event subscribers, CLI commands, background workers).
2) Codebase Exploration & Symbol Search
  1. Search the repository for relevant routes, controllers, schemas, database models, background jobs, and existing tests.
  2. Identify existing patterns, conventions, and reusable utilities in the codebase.
3) Map Dependency & Data Flow
  1. Trace request pathways from entry (HTTP/CLI/Event) through business logic layers down to storage and third-party services.
  2. Map incoming payloads to domain models and outgoing responses.
4) Highlight Technical Risks & Unknowns
  1. Identify legacy technical debt, missing test coverage, breaking change vectors, and unconfirmed assumptions.
  2. Highlight complex integration boundaries or potential performance bottlenecks.
5) Produce Wayfinder Orientation Brief
  1. Output a structured summary (wayfinder.md) covering:
    • System Context: Overview of affected subsystems.
    • Affected Modules: Explicit file paths and components.
    • Key Architectural Constraints: Security, data integrity, UUIDv7 primary keys, and performance boundaries.
    • Critical Unknowns: Specific questions to be resolved during grilling or technical research.

Outputs

  • wayfinder.md: Orientation brief detailing codebase mapping, entrypoints, data flows, and critical unknowns.

Review gate

  • Codebase entry points and file targets verified via code search and file viewing.
  • Data flows and system boundaries mapped.
  • UUIDv7 identity standard specified for entity identifiers.
  • Critical unknowns documented to feed Phase 2 grilling and technical research.

References

  • ../../../SKILL.md
  • ../grilling/SKILL.md
  • ../../embed-aihero-radioactive/SKILL.md

Frequently asked questions

What does the Wayfinder AI skill do?

Strategic orientation, codebase mapping, architectural entry point identification, and intent framing prior to grilling, research, or prototyping.

Why use Wayfinder on TypingMind?

Because you install it once and use it with any model. Wayfinder is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Wayfinder in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/devton/agentic-workflow-blueprint/tree/main/workflows/mattpocock/wayfinder. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Wayfinder?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Wayfinder?

As many as you like. As long as a model supports skills, you can use Wayfinder with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Wayfinder AI skill free?

It is published on GitHub by devton. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇