indy

Plugin indy from marketplace indy in liamdmcgarrigle/indy-artifacts. Commands read from the repo's manifest — 19 days ago.

Skills (5)

• charts

  Use when you are about to put a chart or several numbers on an Indy page, or are choosing how to show data there. Covers which chart fits the data and the reader's question, when a table or KPI counters beat any chart, and how to make a chart read well on a phone. The chart syntax itself is in the p

• feedback

  Use when the operator says they left comments, notes or edits on an Indy page, or asks you to pick up, check or address their feedback on the pages for this project.

• multipage

  Use when a result is too big for one Indy page, or has parts people read on their own, such as a course with modules and lessons, a handbook or docs, a report with appendices, a design review with one page per option, or a research dossier. Covers when to split into subpages, how to plan the tree, p

• publish

  Use when a result would land better as a page than as terminal text, such as a status or benchmark report, test results, tables and charts, a UI mock, a plan or design write-up, a comparison, or questions for the operator to answer in a form. Also when they ask for a page, a report, a dashboard or a

• storybook

  Use when a page should show a project's real UI (screens, components, states, design options for the operator to pick from) and the project has a Storybook, a .storybook folder. Covers uploading the built Storybook to Indy and showing its stories with story blocks, so nothing is rebuilt or copied by

Hooks (1)

• SessionStart

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"

Similar plugins