SkillsAdd

daemon-blockint-tech/agentic-enteprises-skill

senior-software-engineer

Guides senior software engineering across languages and stacks—system and service design, RFCs, code review, refactoring, reliability patterns, testing strategy, performance analysis, technical decomposition, and engineering leadership on delivery teams. Use when designing services or modules, writing technical specs, reviewing PRs for architecture and correctness, improving legacy code, choosing trade-offs (coupling, consistency, latency), estimating complex work, or mentoring engineers—not fo…

First seen May 20, 2026

Installation

$ npx skills add daemon-blockint-tech/agentic-enteprises-skill --skill senior-software-engineer
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from daemon-blockint-tech/agentic-enteprises-skill · top by installs.

npx skills add daemon-blockint-tech/agentic-enteprises-skill
code-security 51 reverse-engineer 50 business-analyst 47 life-health-insurance 45 ontology-engineer 41 wms-developer 40 business-consultant 40 senior-frontend-software-engineer 38 senior-system-architecture 38 web-pentester 38

Browse all from daemon-blockint-tech/agentic-enteprises-skill

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 8
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,678 B
  • docs SUMMARY.md 888 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 35 installs

SKILL.md

Senior Software Engineer

When to Use

  • Design services, modules, APIs, or technical approaches across general software stacks
  • Write RFCs, technical specs, decomposition plans, or engineering trade-off analysis
  • Review PRs for correctness, maintainability, reliability, operability, and test coverage
  • Refactor legacy code safely while preserving behavior
  • Mentor engineers on implementation quality, estimates, and delivery risks

When NOT to Use

  • Build stack-specific full-stack product features end to end → senior-fullstack-developer, fullstack-software-engineer
  • Focus only on React/UI architecture and accessibility → senior-frontend-software-engineer
  • Choose rollout plans, canaries, or cutover strategy → deployment-strategist
  • Provision infrastructure, Kubernetes, or IaC → infrastructure-engineer
  • Make enterprise-wide architecture decisions or ADR review gates → senior-system-architecture

Related skills

Need Skill
React/Next + vertical feature delivery fullstack-software-engineer, senior-fullstack-developer
Senior front-end architecture and a11y senior-frontend-software-engineer
Rollout plans and release strategy deployment-strategist
CI/CD implementation devops
Cloud/K8s/Terraform infrastructure-engineer
Requirements and BRDs business-analyst
AI/LLM product features ai-engineer
Cross-service ADRs, NFRs, architecture review senior-system-architecture
Profiling, load tests, latency SLOs performance-engineer

Core Workflows

1. Technical design (RFC)

  1. State problem, constraints, and non-goals
  2. List options with trade-offs (at least two alternatives)
  3. Recommend one; define interfaces and data contracts
  4. Identify risks: scale, failure modes, migration, operability
  5. Define success metrics and rollout approach (link deployment-strategist if needed)

Deliverable: short RFC or design doc with diagram (C4 or sequence for critical paths).

See references/system_design.md for templates, boundaries, and consistency patterns.

2. Implementation planning

Break work into:

Slice Outcome
Foundation Types, interfaces, skeleton with tests
Core behavior Happy path end-to-end
Edge cases Errors, idempotency, authz
Operability Logs, metrics, runbooks
Cleanup Remove flags, deprecate old path

Estimate each slice; call out unknowns and spikes.

See references/rfctechnicalleadership.md for estimation and decomposition.

3. Code review (senior bar)

Review order: correctness → design → operability → style.

Check Question
Correctness Edge cases, races, error handling
API design Clear contracts, backward compatibility
Security Authz, injection, secrets
Tests Meaningful cases, not snapshot noise
Operability Logs, metrics, configurable limits
Maintainability Coupling, naming, duplication

Leave actionable comments; distinguish blocker vs nit.

See references/code_review.md for rubric and comment patterns.

4. Refactoring and quality

When to refactor: before adding feature in tangled module, or when change touches same area third time.

Approach:

  1. Add characterization tests around behavior
  2. Small commits: extract → rename → move
  3. Preserve external behavior; use feature flags for risky swaps
  4. Delete dead code in same PR when safe

See references/refactoring_quality.md for smells and safe sequences.

5. Reliability and performance

Reliability defaults:

  • Timeouts on all outbound calls
  • Retries with jitter only for idempotent ops
  • Circuit breakers at integration boundaries
  • Graceful degradation with clear user messaging

Performance:

  1. Measure (profiler, traces, query plans)—no premature optimization
  2. Fix N+1, unnecessary allocation, hot loops
  3. Cache with explicit TTL and invalidation story

See references/reliability_patterns.md for distributed systems primitives.

6. Technical leadership

  • Unblock others: pair on hard bugs, clarify design decisions in writing
  • Raise risks early; propose phased delivery
  • Document decisions in ADR when reversal is costly
  • Align with product on scope vs quality trade-offs

See references/rfctechnicalleadership.md for ADRs and mentoring prompts.

When to load references

  • Service design and RFCs → references/system_design.md
  • PR review → references/code_review.md
  • Refactoring → references/refactoring_quality.md
  • Reliability and performance → references/reliability_patterns.md
  • Estimation, ADRs, mentoring → references/rfctechnicalleadership.md