prompt-proximity-architecture

Designs budget-aware prompt coverage blueprints across proximity bands, journey states, and measurement lanes.

663|47|Updated May 19, 2026
One-click install
npx skills add https://github.com/elvisun/newsjack --skill prompt-proximity-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompt-proximity-architecture
Source: https://github.com/elvisun/newsjack/tree/main/skills/prompt-proximity-architecture
Command: npx skills add https://github.com/elvisun/newsjack --skill prompt-proximity-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Measuring AI visibility requires deciding which prompts to run before writing any prompt wording. This Skill turns a measurement charter, ICP hypotheses, and buyer jobs into a structured coverage blueprint that defines required, optional, and prohibited intent cells, preventing unsupported or contaminated prompt coverage.

Core Features & Use Cases

  • Proximity band assignment: Classifies intent cells into six structural bands (B0 brand through B5 market) with correct aided-status rules and contamination handling.
  • Budget-aware allocation: Stratifies coverage across jobs, journey states, information acts, roles, locales, evidence grades, partitions, and measurement lanes, returning allocation conflicts instead of silently dropping coverage.
  • Prohibited-cell enforcement: Blocks cells that fabricate categories, misuse aided stimuli, or derive core prompts from AI answers or target pages.
  • Use Case: Given an approved measurement charter and buyer job evidence, produce a prompt_architecture.json with 30–48 unaided diagnostic cells plus a Markdown coverage summary, ready for handoff to prompt generation.

Quick Start

Use the prompt-proximity-architecture skill to design a prompt coverage blueprint from my measurement charter, ICP hypotheses, and buyer jobs within a 60-cell budget.

Frequently Asked Questions about prompt-proximity-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design prompt coverage for AI visibility measurement?

Start from an approved measurement charter, ICP hypotheses, and buyer jobs, then define intent cells across proximity bands, information acts, journey states, roles, and locales. Allocate cells to fit your run budget and mark unsupported combinations as prohibited rather than generating a full Cartesian grid.

What are prompt proximity bands in AI visibility tracking?

Proximity bands classify prompts by structure: B0 names the brand, B1 covers shortlists and comparisons, B2 names a category, B3 describes a problem, B4 states a goal, and B5 covers market trends. They are structural labels, not a funnel scale, and each band has a default aided status.

How many prompt cells should an AI visibility panel include?

A diagnostic default targets 30–48 unique unaided cells with two variants per cell and three repeats per wave, while a standard panel targets 60–120 cells. Adjust to budget and keep aided cells outside the unaided quota.

Can I treat prompt proximity bands as a marketing funnel?

No. Bands are structurally different prompt types, not funnel stages: B0 can be post-purchase, B3 can describe an urgent funded decision, and B1 can be early exploration. The funnel field may be null and must never drive the schema.

What happens when the budget cannot cover all required prompt cells?

The skill returns an allocation conflict instead of silently dropping a band, role, locale, or control. You must either raise the budget, obtain an explicit waiver, or narrow the charter's required coverage.