All authors
Claude Skills by nimbalyst
github.com/nimbalyst26 skills0 installs6 views
- AnimationAuthor animated technical explainer diagrams as .anim.json files for Nimbalyst's Animation editor. Use when the user wants to animate a diagram, show how a system/protocol/algorithm behaves over time, build a motion explainer, or turn a static architecture diagram into something that plays.Votes: 0GitHub stars: 1,842
- CanvasAuthor Nimbalyst Project Canvas boards (.canvas files) — an infinite canvas whose cards are live editors for real workspace files and shared documents, arranged spatially and wired with edges. Use when the user asks for a canvas, a board, a spatial layout of documents or mockups, a flow of screens, or a workspace overview.Votes: 0GitHub stars: 1,842
- DatamodellmCreate visual data models for database schemas using Nimbalyst's DataModelLM editor. Use when the user wants to design a data model, database schema, entity relationship diagram, or Prisma schema.Votes: 0GitHub stars: 1,842
- Git CommitCreate git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead.Votes: 0GitHub stars: 1,842
- ExcalidrawCreate diagrams and visual drawings using Excalidraw (.excalidraw files). Use when the user wants flowcharts, architecture diagrams, system diagrams, sketches, or any visual diagram. For database schemas and entity relationship diagrams, use the DataModelLM extension instead.Votes: 0GitHub stars: 1,842
- Extension DevelopmentBuild, install, and hot-reload Nimbalyst extensions using MCP tools. Use when developing, testing, or iterating on Nimbalyst extensions.Votes: 0GitHub stars: 1,842
- Feedback IntakeHelp the user file a bug report or feature request for Nimbalyst. Activates when the user opens the in-app feedback flow or runs /feedback:bug-report or /feedback:feature-request. Coordinates evidence gathering, anonymization, and posting to GitHub Issues.Votes: 0GitHub stars: 1,842
- MockuplmCreate visual UX mockups using HTML/CSS files (.mockup.html). Use when the user wants to design UI, wireframes, visual layouts, or plan features visually.Votes: 0GitHub stars: 1,842
- PlanningCreate structured plan documents and track work items using YAML frontmatter. Use when the user wants to plan a feature, track progress, log bugs/tasks/ideas, or organize project work.Votes: 0GitHub stars: 1,842
- Knowledge GraphWrite a project's knowledge pages in Nimbalyst Pages -- record what people said and decided in the page it affects, keep typed pages for the things the team tracks (its own types, such as modules, technologies, competitors), and connect typed pages with named relations written as links. Follows the project's "How we write this wiki" page. Use when the user wants to record decisions, open questions or context in the project's pages, wiki or knowledge base, add or restructure pages, or migrate ...Votes: 0GitHub stars: 1,842
- Knowledge SetupSet up or check a project's knowledge pages in Nimbalyst Pages -- install the editable "How we write this wiki" guide page, define the team's own page types (and subtypes) and the named relations between them, and report content from the earlier knowledge graph without changing it. Safe to re-run; it never overwrites or deletes. Use when the user wants to start a team wiki or knowledge base, add a type or a relation, or check that an existing setup is complete. To write pages, use the knowled...Votes: 0GitHub stars: 1,842
- Knowledge GraphWrite a knowledge graph in Nimbalyst trackers -- entities, claims, questions, findings, investigations, the labels that say what each page is, and the predicates that connect them -- following the project's wiki guide. Use when the user wants to record what is known about products/systems/decisions in the team wiki or knowledge base, or to add pages, statements, questions, or findings to an existing graph. To set up a new graph or add a vocabulary pack, use the knowledge-setup skill.Votes: 0GitHub stars: 1,842
- Knowledge SetupInitialize or repair a project's knowledge graph in Nimbalyst trackers -- define the entity, claim, question, finding, and investigation kinds, merge the core vocabulary pack (and the market or spec pack when asked) into the label and predicate registries, create the wiki home page, and install the "How we write this wiki" guide page. Safe to re-run; it never overwrites or deletes. Use when the user wants to start a team wiki or knowledge base, add a vocabulary pack, or check that an existing...Votes: 0GitHub stars: 1,842
- Wiki KeeperKeep the repository's Nimbalyst team wiki current while you work. Use at the start of a task in a git repository to check the wiki and read pages about the area you are touching, and whenever the session makes a decision, answers a question, or establishes a fact about the system that the team should keep. Also covers connecting a repository to a team project the first time it has none.Votes: 0GitHub stars: 1,842
- Knowledge GraphWrite a project's knowledge pages in Nimbalyst Pages -- record what people said and decided in the page it affects, keep typed pages for the things the team tracks (its own types, such as modules, technologies, competitors), and connect typed pages with named relations written as links. Follows the project's "How we write this wiki" page. Use when the user wants to record decisions, open questions or context in the project's pages, wiki or knowledge base, add or restructure pages, or migrate ...Votes: 0GitHub stars: 1,842
- Knowledge SetupSet up or check a project's knowledge pages in Nimbalyst Pages -- install the editable "How we write this wiki" guide page, define the team's own page types (and subtypes) and the named relations between them, and report content from the earlier knowledge graph without changing it. Safe to re-run; it never overwrites or deletes. Use when the user wants to start a team wiki or knowledge base, add a type or a relation, or check that an existing setup is complete. To write pages, use the knowled...Votes: 0GitHub stars: 1,842
- ConnectConnect this repository to its Nimbalyst team project so the session can read and write the team's pages. Use at the start of a task in a git repository before any Pages tool, when a Pages tool returns repo_not_bound, ambiguous_project, pin_mismatch, project_not_accessible or admin_required, or when the user asks to connect a repository to a team project. How to write pages is in the knowledge-graph skill.Votes: 0GitHub stars: 1,842
- Knowledge GraphWrite a project's knowledge pages in Nimbalyst Pages -- record what people said and decided in the page it affects, keep typed pages for the things the team tracks (its own types, such as modules, technologies, competitors), and connect typed pages with named relations written as links. Follows the project's "How we write this wiki" page. Use when the user wants to record decisions, open questions or context in the project's pages, wiki or knowledge base, add or restructure pages, or migrate ...Votes: 0GitHub stars: 1,842
- Knowledge SetupSet up or check a project's knowledge pages in Nimbalyst Pages -- install the editable "How we write this wiki" guide page, define the team's own page types (and subtypes) and the named relations between them, and report content from the earlier knowledge graph without changing it. Safe to re-run; it never overwrites or deletes. Use when the user wants to start a team wiki or knowledge base, add a type or a relation, or check that an existing setup is complete. To write pages, use the knowled...Votes: 0GitHub stars: 1,842
- CaptureRecord what people decided in this session in the wiki pages it affects (team or local wiki). Use when the user asks to capture or record what the session decided, or when a wiki reminder asks you to.Votes: 0GitHub stars: 2
- ConnectChoose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns repo_not_bound, ambiguous_project, pin_mismatch, project_not_accessible, admin_required or "No local wiki", or when the user asks to connect a repository or start a wiki. How to write pages is in the update skill.Votes: 0GitHub stars: 2
- RecallAnswer from the project's wiki what was decided, why, and what it says about an area. Use when the user asks "why did we", "what did we decide", "is there a decision on" or "what does the wiki say", and before starting design or a non-trivial change in an area the wiki may cover.Votes: 0GitHub stars: 2
- SetupCreate a project wiki with a useful Home, starter pages, and a writing guide.Votes: 0GitHub stars: 2
- StartStart using Nimbalyst Wiki: show how agents build a local wiki, capture decisions, track typed pages, open the local browser view, and optionally use a team wiki. Use when the user asks what this plugin does, which skills it has, or how to begin.Votes: 0GitHub stars: 2
- TeamPut this project's wiki on Nimbalyst Teams: sign in, create or choose the team project, move the local wiki into it in one step, open it in the browser, and invite teammates. Use when the user asks to move the local wiki to Teams, share the wiki with their team, create a team, or invite people to the wiki.Votes: 0GitHub stars: 2
- UpdateWrite and maintain project wiki pages, decisions, and links. Use for any wiki page, including architecture or product maps, diagrams, HTML pages and other visuals, and before changing code a page covers.Votes: 0GitHub stars: 2