fernworks
Official@fern-works
fernworks publishes 44 engineering-discipline skills covering code review, TDD, architecture decision records, domain modeling, and repository planning for software teams.
Agent Skills by fernworks
Showing 6 vetted skills indexed across 1 GitHub repositories.
fern-worksdiagram-design
Create branded diagrams as standalone HTML, SVG, or PNG files from 40 visual types.
fern-worksarchitecture-map
Builds an interactive isometric map of a repository's architecture with measured snapshots and staleness tiers.
fern-workscode-review
Reviews a git diff against documented coding standards and the originating spec in parallel sub-agents.
fern-worksprinciple-boundary-discipline
Concentrates validation and error handling at system boundaries while keeping business logic in pure functions.
fern-worksprinciple-model-the-domain
Encodes domain rules in data structures instead of scattered conditionals across code.
fern-worksprinciple-type-system-discipline
Applies type system patterns to eliminate illegal states and unhandled variants in statically-typed code.
Frequently Asked Questions About fernworks
FAQPage SchemaWhat tasks can I accomplish using fernworks skills?▼
You can review branches and PRs against repo standards and specs, run test-driven development cycles, prune test suites with mutation proof, diagnose bugs and performance regressions, model domains, record ADRs, decompose plans into tickets, and generate architecture maps and diagrams.
Who are fernworks skills designed for?▼
Software engineers, tech leads, and reviewers working in statically-typed codebases who need disciplined practices: boundary validation, type-system design, concurrency reasoning, over-engineering review, and evidence-based verification of claims.
How do fernworks planning skills work in practice?▼
Skills like to-spec and to-tickets synthesize the current conversation into a spec.md and tracer-bullet ticket files under .greenline/work/, each ticket declaring depends_on edges. The implement skill then builds one frontier ticket per fresh context.
What prerequisites do fernworks skills require?▼
A repository with an engineering purpose; several skills expect a .greenline/ directory structure for tickets, specs, decisions, maps, and diagrams. Review skills require a committed range, branch, tag, or merge-base plus documented repo standards.
How do fernworks skills handle verification and code quality?▼
verify-this restates claims falsifiably, captures baseline and treatment, and returns VERIFIED, NOT VERIFIED, or INCONCLUSIVE. ponytail-review hunts over-engineering—reinvented stdlib, unneeded dependencies, speculative abstractions—with one deletion finding per line.