Technical Writing

Write self-documenting code with clear structure and naming, adding minimal, helpful, evergreen comments only for large sections of complex logic, avoiding comments about recent changes or temporary fixes. Use this skill when writing or reviewing code in any file where comments or code documentation are involved. Apply when deciding whether to add comments, when refactoring code to be more self-explanatory through better naming and structure, when reviewing existing comments for relevance and evergreen quality, when removing outdated or change-related comments, or when adding concise explanatory comments for complex logic sections. Use for any task involving code documentation strategy, comment quality assessment, or improving code readability through structure rather than comments.

Expert guidance for writing secure, reliable, and performant Claude Code hooks - validates design decisions, enforces best practices, and prevents common pitfalls

IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation

Read documentation from the server-side noridocs system by file path.

Use this when you have finished making code changes and you are ready to update the documentation based on those changes.

Sync all local docs.md files to server-side noridocs system.

Search the Nori knowledge base for relevant context, solutions, and documentation.

List all server-side noridocs, optionally filtered by repository and/or path prefix.

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

Write or update documentation in the server-side noridocs system.

Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts

Applies the Diataxis framework to create or improve technical documentation. Use when being asked to write high quality tutorials, how-to guides, reference docs, or explanations, when reviewing documentation quality, or when deciding what type of documentation to create. Helps identify documentation types using the action/cognition and acquisition/application dimensions.

Practical bash scripting guidance emphasising defensive programming, ShellCheck compliance, and simplicity. Use when writing shell scripts that need to be reliable and maintainable.

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behaviour, production pollution with test-only methods, and mocking without understanding dependencies

Extract wisdom, insights, and actionable takeaways from text sources. Use when asked to analyse, summarise, or extract key learnings from blog posts, articles, markdown files, or other text content.

Applies current Go testing best practices. Use when writing or modifying Go test files or advising on Go testing strategies.

This skill should be used when writing or reviewing Swift code for iOS or macOS projects. Apply modern Swift 6+ best practices, concurrency patterns, API design guidelines, and migration strategies. Covers async/await, actors, MainActor, Sendable, typed throws, and Swift 6 breaking changes.

Manage GitHub issues locally as Markdown files. Use for triaging, searching, editing, and creating issues without leaving your editor or terminal.