Prompt Proximity Architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt...
Install
npx skills add elvisun/newsjack --skill prompt-proximity-architecture -g -a claude-code -y- Repository
- elvisun/newsjack1.7k
- Category
- AI and agents
- Updated
- 10d ago
- License
- MIT
- Context cost
- Mediumabout 1,827 tokens
- Runs scripts
- No, instructions only
What it does
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited canonical intent cells.
Prompt Proximity Architecture
Design the cells before writing the strings.
This skill inherits the ethical floor from skills/ETHICS.md. It enforces anti-hallucination and evidence-bound coverage. Anti-spray and human-send are not applicable.
Inputs
Require:
- a measurement charter;
- approved
icp_hypotheses.jsonandbuyer_jobs.json; - target run/review budget;
- required locales, surfaces, and lanes;
- any campaign partition and prior-panel constraints.
If the charter is provisional, design a provisional architecture and name the gaps. Reject a charter that says only “track AI visibility.”
Keep dimensions independent
Each intent cell fixes:
- buyer job;
- information act;
- journey state;
- material constraints;
- persona or buying role;
- locale and language;
- prompt-proximity band;
- expected answer kind.
Add independent tags for evidence grade, partition, lane eligibility, turn form, and optional funnel. Do not make funnel the schema.
Use the supported acts explain, diagnose, plan, generate, compare, recommend, verify, navigate, buy, implement, and troubleshoot. Include only acts entailed by the job evidence.
Use journey states problem_identification, exploration, requirements_building, supplier_selection, adoption, and post_purchase.
