skills.rest
hackefeller
hackefellerOFFICIAL
Explore all skills by this author →
WebsiteGitHub

apps-database-access

Define canonical data-access patterns for apps data fetching and mutations.

1|Updated Sep 2, 2019
Search Tags:#patterns#guidelines#mutations#data-access#apps#data-fetching#api-contracts
One-click install
npx skills add https://github.com/hackefeller/hominem --skill apps-database-access
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apps-database-access
Source: https://github.com/hackefeller/hominem/tree/main/.codex/skills/apps-database-access
Command: npx skills add https://github.com/hackefeller/hominem --skill apps-database-access

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonically guides developers on consistent data-access patterns for apps/** work that involves fetching, mutating, or negotiating API contracts.

Core Features & Use Cases

  • Canonical data-access patterns: guidelines for data fetching and mutations across frontend and backend in apps/**
  • API contract alignment: standards for API definitions, types, and versioning
  • Quality and testing guidance: recommended tests, error handling, and performance considerations

Quick Start

Follow the canonical data-access guidance to implement the data-fetching and mutation layer for a new apps/** feature, ensuring consistent API contracts and robust error handling.

Frequently Asked Questions about apps-database-access

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

FAQPage Schema
What are canonical data-access patterns for apps fetching and mutating data?▼

Canonical data-access patterns provide standardized guidelines for data fetching and mutations across apps/** work, defining naming conventions, error handling, and testing strategies for frontend and backend implementations.

How do I align API contracts for Node, React, GraphQL, and REST services?▼

Align API contracts by applying standards for API definitions, types, and versioning across Node, React, GraphQL, and REST services to ensure consistent data access layers and contract validation.

Does this data-access guidance work for both frontend and backend tasks?▼

Yes, the data-access guidance is applicable to both frontend and backend tasks, covering API adapters, data fetching, mutations, and contract validation across React, Node, GraphQL, and REST services.

What's the best way to implement error handling and testing for data-access layers?▼

Implement error handling and testing by following the guidance's recommended tests, error handling strategies, and performance considerations to ensure robust data fetching and mutation layers in apps/** work.

When do I need canonical data-access guidance for data fetching and mutations?▼

You need canonical data-access guidance when implementing data access layers, API adapters, or contract validation in apps/** work, ensuring consistent patterns and guardrails across the codebase.

Related Skills

Explore More Software Engineering Skills→
VeradelaCruzVeradelaCruz

api-design

Define API requirements and generate OpenAPI or GraphQL schemas.

Community
Intermediate
kevinreberkevinreber
3

api-endpoint

Create REST API endpoints with Zod validation and route naming conventions.

Community
Advanced
kqcoxnkqcoxn
369

coding-standards

Enforce TypeScript, JavaScript, React, and Node.js coding standards across projects.

Community
Intermediate
omakeiomakei
2

nuxt-features

Modularize domain logic into feature-based Nuxt modules with queries, mutations, and actions.

Community
Intermediate