iainmcl/diagram
claude/skills/diagram/SKILL.md
Create FigJam diagrams for documentation and flow mapping — user flows, system flows, architecture diagrams, process maps, and brainstorming boards. Not for UI design or wireframing.
documentation
Updated May 1, 2026
$ install --global
skillsauthnpx skillsauth add iainmcl/dotfiles diagramInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 10:38 AM62.5s1 file scanned
SKILL.md
- name:
- diagram
- description:
- Create FigJam diagrams for documentation and flow mapping — user flows, system flows, architecture diagrams, process maps, and brainstorming boards. Not for UI design or wireframing.
Diagram Creator
Creates clear, readable FigJam diagrams for documentation and flow mapping using the Figma MCP.
Use cases
- User flows and journey maps
- System and architecture diagrams
- Process maps and swimlane diagrams
- Brainstorming and ideation boards
- Technical documentation visuals
Process
- Understand the subject — ask clarifying questions if the scope or audience is unclear before starting.
- Choose the right diagram type — pick the simplest format that communicates the idea clearly (flowchart, swimlane, mind map, etc.).
- Use FigJam conventions — flowchart shapes, connectors, sticky notes, sections, and simple labels. Avoid decorative elements that add noise.
- Label clearly — every node, connector, and section should be labelled. Assume a non-technical reader may need to understand it.
- Keep it readable — prefer clarity over completeness. If a diagram is getting complex, split it into multiple focused diagrams.
Constraints
- Do not create UI designs or wireframes — direct those requests to the
ux-ui-designeragent. - Do not over-engineer diagrams with unnecessary detail.
Related Skills
iainmcl/weekly-review
development
VerifiedTrustedCommunity
Run a weekly achievement review - pulls from Jira, GitHub, and Slack to capture what you shipped in the last week, maps achievements to your 2026 goals, and appends impact-focused entries to your brag doc. Use when asked to "do a weekly review", "capture this week's wins", "update my brag doc", "what did I ship this week", "record my achievements", "what have I done this week", "add to my performance doc", or anything about tracking weekly progress, brag doc entries, or performance evidence. Trigger even if the user just says "weekly review" or "document what I did".
SKILL.mdUpdated May 19, 2026
iainmcl/skill-creator
testing
VerifiedTrustedCommunity
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
SKILL.mdUpdated May 19, 2026
iainmcl/setup-project-update
tools
VerifiedTrustedCommunity
Set up a project update config for the current repo, so that running project-update requires no setup questions. Use when asked to "set up project updates", "configure project update", "initialise project update", or "create a project update config". Run this once per project repo.
SKILL.mdUpdated May 19, 2026
iainmcl/sentry-fix
testing
VerifiedTrustedCommunity
Find the highest-frequency unresolved Sentry error for the VAT & Invoicing or Billing team, understand its root cause, create a Jira ticket in the APP project, implement a fix, and open a draft PR. Use when asked to "fix sentry issues", "triage sentry errors", "look at sentry", "what's broken in sentry", "create a fix for a sentry issue", or "sentry triage". Runs the full flow autonomously in the background.
SKILL.mdUpdated May 19, 2026