skills.rest
Lin117-shygo
Lin117-shygoCOMMUNITY
Explore all skills by this author →
GitHub

before-backend-dev

Guide backend tasks by consulting guideline files for database, error handling, logging, and type-safety.

Updated Mar 6, 2026
Search Tags:#database#logging#backend#guidelines#type-safety#error-handling#coding-standards
One-click install
npx skills add https://github.com/Lin117-shygo/ros_car --skill before-backend-dev-lin117-shygo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: before-backend-dev
Source: https://github.com/Lin117-shygo/ros_car/tree/main/.agents/skills/before-backend-dev
Command: npx skills add https://github.com/Lin117-shygo/ros_car --skill before-backend-dev-lin117-shygo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a structured kickoff guide for backend development standards.

Core Features & Use Cases

  • Guideline-driven kickoff: directs developers to the central guidelines repository.
  • Task alignment: highlights the specific guideline files for database work, error handling, logging, and type-safety.
  • Compliance assurance: helps teams enforce standards before coding begins.

Quick Start

Open .trellis/spec/backend/index.md to review guidelines, then follow the relevant files (database-guidelines.md, error-handling.md, logging-guidelines.md, type-safety.md) to start your backend task.

Frequently Asked Questions about before-backend-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are backend development standards for database and error handling?▼

Backend development standards provide structured guidelines for database work, error handling, logging, and type-safety to ensure consistent code quality before implementation begins.

How do I start a backend coding task using standard guidelines?▼

To start a backend coding task, open the backend index guidelines, then follow the specific files for database, error handling, logging, and type-safety to align your implementation.

Do I need to review type-safety and logging guidelines before writing backend code?▼

Yes, you need to review type-safety and logging guidelines before writing backend code to enforce team compliance and ensure structural standards are met from the kickoff.

What is the best way to enforce coding standards across backend projects?▼

The best way to enforce coding standards across backend projects is using a centralized kickoff guide that directs developers to specific database, error handling, and logging guideline files.

Can I apply these backend guidelines to any software engineering project?▼

Yes, you can apply these backend guidelines to any software engineering project, as they are designed to be applicable to backend tasks across different projects.

Why should I consult backend guidelines before starting database work?▼

You should consult backend guidelines before starting database work to ensure your implementation aligns with predefined type-safety, error handling, and logging standards from the beginning.

Related Skills

Explore More Software Engineering Skills→
taku-otaku-o
1

kiro-spec-init

Initialize structured project specifications from briefs into .kiro/specs directories.

Community
Intermediate
TbK0ngTbK0ng

before-backend-dev

Enforce backend development guidelines before implementation via documentation review and planning.

Community
Intermediate
Serg28Serg28

fullstack-guardian

Implement secure full-stack web features with frontend UI, backend APIs, and layered validation.

Community
Advanced
mwathibenmwathiben

typescript-review

Review TypeScript and JavaScript diffs against Metabase coding standards.

Community
Intermediate