← all publishers

truong-v

@truong-v source repo

Report this profile Claim this profile

• 3 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Orchestrate · truong-v

   Execute an already-approved plan in tech-lead orchestration mode: turn the plan into a delegation map across deep-reasoner / balanced-implementer / fast-worker, dispatch self-contained briefs (parallel where possible), then verify and synthesize the results. Use ONLY when the user invokes /orchestrate or explicitly asks to "apply the orchestration", run in "tech-lead mode", or "orchestration mode" — typically right after approving a plan built with Fable in plan mode. Do NOT trigger for ordinary multi-step tasks the user has not asked to orchestrate.
   0 installs
2. ▌
   Report HTML · truong-v bundle

   Turn a report, spec, findings write-up, research brief, analysis, memo, proposal, or postmortem into ONE rich, interactive, self-contained HTML page — executive summary, key-findings cards, sortable data tables with inline SVG charts, numbered citations with popovers, tabbed comparisons, status/severity badges, a sticky table of contents, collapsible detail, and callouts. Reach for this whenever the user wants to write, format, present, or hand off written or analytical material as a polished shareable document rather than a wall of Markdown — e.g. "write up these findings", "turn my notes into a report", "draft a spec", "make a research brief on X", "put together a readout for leadership". Use it whether they supply the substance (notes, data, a draft) or just a topic to draft from, and especially when they want it detailed, visual, interactive, or shareable. For pure code explanations use explain-code-html; for chart design load dataviz.
   0 installs
3. ▌
   Explain Code HTML · truong-v bundle

   Generate a rich, interactive, self-contained HTML page that explains code — annotated syntax-highlighted source, collapsible sections, a table of contents, an interactive step-through of the key path, and inline SVG diagrams. Reach for this whenever the user wants to understand, explain, walk through, visualize, or document how code works — a snippet, a function, a whole file, an algorithm, a subsystem across files, or a concept or behavior you must first track down in a codebase (e.g. "how does caching work in this service", "walk me through the request lifecycle"). Especially use it when they want the explanation detailed, visual, interactive, or shareable rather than a few lines of terminal text, or when they ask for an "HTML explanation", "interactive walkthrough", or "visual explanation" — even if they never say the word "HTML". Prefer it over plain text whenever a diagram or clickable annotations would make code click faster than prose.
   0 installs