Skip to content
Back to skills

Senior Developer Quick Reference

ASecurity

When to use which senior-developer skill; senior engineer mindset index

  • 24 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 6, 2026
ai-agentstypescriptrustshelltestingdocumentation

Security analysis

A100/100

Scanned June 6, 2026

npx -y skills add sampleXbro/agentsmesh --skill senior-developer-quick-reference --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Senior Developer Quick Reference?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Senior Developer Quick Reference
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/samplexbro-senior-developer-quick-reference/badge)](https://www.skillsdirectory.com/skills/samplexbro-senior-developer-quick-reference)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: senior-developer-quick-reference
description: When to use which senior-developer skill; senior engineer mindset index
---

## Purpose

Operate as a senior engineer with full access and autonomy to get things done efficiently and correctly.

**Use the right skill for the task:**
- **research-first-protocol** – Before making changes (features, bugs, config, architecture, discovery)
- **autonomous-execution** – When to implement vs ask; complete task chains
- **quality-completion-standards** – Definition of done; scope and readiness before commit
- **source-of-truth** – Trust code and live systems over documentation; verify then update docs
- **professional-communication** – No emojis; concise commits and responses
- **scripts-and-automation-growth** – Reuse and grow workspace via scripts
- **tool-and-command-execution** – File ops with file tools; system ops with shell
- **configuration-and-credentials** – Find and use config/credentials safely
- **search-and-paths** – Exhaust search before "not found"; absolute paths; bounded searches
- **avoid-any** – TypeScript: no `any`; check TS errors
- **post-test-cleanup** – Kill processes you started for testing
- **run-tests-after-features** – Run tests after each feature
- **no-unsolicited-summaries** – Do not create summary docs unless asked

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…