alexvtejeda

@alexvtejeda source repo

8 skills
0 followers
16 hours ago last updated

▌
Elenchus Gather · alexvtejeda bundle
Use when the user wants to build a CLOSED CORPUS of real, verified resources or links by fanning out parallel agents — "gather as many X links as possible", "harvest a curated set of sources", "build a closed space of playlists/repos/feeds for a model (or person) to choose from", "collect verified URLs across these categories". The harvest front end over the elenchus-council engine. NOT for stress-testing a build premise (elenchus-build), NOT for a reading list to learn a topic (elenchus-study), and NOT for a one-shot lookup (a single search answers that).

0
installs
▌
Elenchus Council · alexvtejeda bundle
Use when a request asks to convene the council, stress-test a premise, or get a multi-seat anonymized critique before committing to a design — or when an Elenchus front-end skill (e.g. elenchus-build) needs to run that review. This is the shared engine: front ends call it; it is not triggered directly by ordinary "write me code" feature requests.

0
installs
▌
Visual Companion · alexvtejeda bundle
Use to SHOW the user something in their browser during an Elenchus or brainstorming flow — UI mockups, wireframes, architecture diagrams, side-by-side visual comparisons, design polish — when the content itself is visual and the user would grasp it better by seeing than by reading. The user always ANSWERS in the terminal; the browser is display-only (no clicking, no selections recorded). Typically dispatched by elenchus-build for a visual frontend-design question, paired with ui-ux-pro-max for the design intelligence. NOT for text/tabular questions (requirements, tradeoff lists, A/B/C described in words) — those stay in the terminal.

0
installs
▌
Finishing Implementation Elenchus · alexvtejeda
Use when a frontend feature has been implemented and you want to verify it actually works in the running browser against its spec/plan — then fix what doesn't — before calling it done. Triggers: "verify my implementation works", "check the frontend against the spec", "did I actually build everything", "finish and verify this feature", "run the finishing pass". The post-execution stage of the Elenchus pipeline. NOT for stress-testing a build premise (elenchus-build), NOT for writing or verifying a plan (elenchus-plan), and NOT a code-style review.

0
installs
▌
Elenchus Tui · alexvtejeda bundle
Use when the user wants a terminal-UI (TUI) mockup designed and then proven to actually render — pure-ASCII, no framework — before building the real thing. Triggers: "mock up a terminal UI for X", "design a TUI / CLI dashboard I can show someone", "make an ASCII wireframe of this terminal app and make sure it renders", "prototype these terminal screens and verify the alignment". Generates one runnable stdlib script with named, navigable breakpoint-states + a `.txt` snapshot per state, then verifies each in an isolated tmux session. NOT the browser/web mockups of visual-companion, NOT stress-testing a build premise (elenchus-build), NOT verifying a finished web feature (finishing-implementation-elenchus).

0
installs
▌
Elenchus Plan · alexvtejeda bundle
Use when you have an approved spec (or firm requirements) for a multi-step build and want the implementation plan itself stress-tested before you execute it — "write the plan and have the council check it", "verify this plan against the spec", "turn this spec into a plan I can trust", or the writing-plans stage of the Elenchus pipeline. The plan/verification front end over the elenchus-council engine. NOT for stress-testing a build PREMISE that isn't settled yet (that's elenchus-build), NOT for authoring plan craft from scratch with no council (that's plain writing-plans), and NOT for verifying a finished implementation in the browser (that's finishing-implementation-elenchus).

0
installs
▌
Elenchus Build · alexvtejeda bundle
Use when the user wants a build or architecture idea stress-tested before they commit to building it — "help me plan/design this app", "design the architecture for X", "review my architecture before I build", "is my mental model of X sound", "I want to build Y because Z — poke holes in it". For the still-articulating stage, before brainstorming. NOT for ideas already decided (that's brainstorming), NOT for researching/learning a topic the user has no premise about yet ("I want to learn about X" / "gather resources on Y" — that's elenchus-study), and NOT for an over-engineering / flaw yes-no verdict ("is X over-engineering?") — a single high-tier model can answer those.

0
installs
▌
Elenchus Study · alexvtejeda bundle
Use when the user wants to research or learn a topic before forming a firm opinion — "I want to learn about X", "help me research Y", "gather a reading list / resources / a study path on Z", "I'm new to X and want to understand it deeply", "convene a research council on X". The research/study front end over the elenchus-council engine. NOT for stress-testing a concrete build/architecture premise the user already intends to construct (that's elenchus-build), and NOT for a one-shot factual lookup (a single search answers those).

0
installs

8 published skills