Agent skill
high-density-writing-style
Guidelines for a writing style that's concise and direct. aka High density language, HD style Use for writing/editing prompts, artefact documents, TDD, PRD, discovery documents, research, AGENTS.md, and more.
Install this agent skill to your Project
npx add-skill https://github.com/rstacruz/agentic-toolkit/tree/main/skill/atk-extras/high-density-writing-style
SKILL.md
High-density writing style
- Optimize for conciseness, brevity, scannability
- Use lists, sentence fragments, broken grammar OK
- Remove unnecessary articles, verbose phrasing
- Direct, high-density language
Example
# User authentication system
**Goal:** Implement secure auth flow with session management
## Requirements
### F1: Login flow
- F1.1: Email/password validation — check format, non-empty
- F1.2: Rate limiting — max 5 attempts per 15min window
### F2: Security
- **Password hashing:** bcrypt with cost factor 12
- **HTTPS only:** reject non-secure connections
- **CSRF protection:** validate tokens on state-changing operations
## Technical approach
**Database schema:**
- `users` table: id, email, password_hash, created_at
- `sessions` table: token_hash, user_id, expires_at, last_active
**Flow:**
1. Client submits credentials
2. Server validates, checks rate limit
3. Generate JWT, create session record
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
refine-implementation
Use after implementation to simplify and review code. Provide: git range (eg, main...HEAD). Runs simplify + peer review loop until change set is clean.
implement-spec
Implements a spec on a ticket-by-ticket basis.
spec-product-requirements
Gives important guidelines to define product requirements sections (functional requirements, technical requirements, constraints, design considerations, diagrams). Companion to $spec-mode.
coding-practices
Contains important guidelines for software engineering, coding, programming. Includes (but not limited to): - CP1: Functional core, imperative shell - CP2: Operational vs unexpected errors - CP3: Result-oriented interface pattern - CP4: Presentational vs container components - CP5: Log context builder pattern Use this when writing, editing, debugging, planning, or otherwise working with: - Any programming work - UI components in React, Vue, or similar - JavaScript, TypeScript, Rust, or any programming language
spec-tech-design
Gives important guidelines to define technical design sections (call graphs, data models, pseudocode, files, CSS classes, testing strategy). Companion to $spec-mode skill.
review-changes
Use when reviewing code changes against a plan. Provide: plan/spec doc; git range or changed files (eg, branch...HEAD). Returns P1/P2/P3 on alignment, quality, bugs, security.
Didn't find tool you were looking for?