achra-guidelines

Achra Platform guidelines, business rules, architecture, and engineering patterns. Use when writing or refactoring Achra code, adding modules or components, creating or updating skeleton loaders, loading placeholders, Suspense fallbacks, or Next.js loading.tsx, answering questions about Achra architecture or business domains, deciding when to use feature flags, applying Achra naming and placement conventions, or answering which technologies and libraries the project uses.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "achra-guidelines" with this command: npx skills add yasielcabrera/achra-guidelines-skill/yasielcabrera-achra-guidelines-skill-achra-guidelines

Achra Guidelines

Overview

Achra platform guidelines for architecture, conventions, business domains, and technical patterns. This skill covers where code lives, how to name and structure it, when to use feature flags, and how domains and routes map.

WIP: These guidelines are a draft. When a task is not covered here or in linked references, prefer consistency with existing Achra code and patterns.

When to Apply

Reference these guidelines when:

  • Writing new code in the Achra codebase (components, pages, services, hooks, providers, etc)
  • Creating skeleton loaders, loading placeholders, Suspense fallbacks, or Next.js loading.tsx
  • Refactoring or reviewing code for Achra consistency
  • Adding a new module, feature, or route
  • Answering questions about Achra architecture, business domains, or conventions
  • Deciding where to place a component or whether to add a feature flag
  • Answering questions about Achra's tech stack or choosing libraries/tools

Quick Reference

TopicRuleDetails
Module placementShared vs domain, promotion rulesUsed in 2+ modules or app root → check Promotion rules; single domain → modules/{domain}/. See architecture.md.
Namingkebab-caseFiles and directories: component-name.tsx, use-hook-name.ts. See conventions.md.
ComponentsDirectory + indexOne dir per component; one component per file (subcomponents in separate files). Helpers in lib/utils, not in component files. Named function, named export. See conventions.md.
Feature flagsShared, env-specificmodules/shared/lib/feature-flags/. Use for gating domains/sections (workstreams, finances, roadmaps). See feature-flags-and-env.md.
Data / GraphQLDomain graphql, generatedQueries in modules/<domain>/graphql/*.graphql; generated in modules/__generated__/graphql/. See data-and-graphql.md.
TypesProps in file; reusable at module rootconventions.md
Tech stackNext 16, React 19, TS, Tailwind 4, shadcn, GraphQL + TanStack QueryFramework, UI, data, forms, and tooling. See tech-stack.md.
Skeleton loadingMirror layout with SkeletonUse Skeleton from @/shared/components/ui/skeleton; place *-skeleton.tsx next to source component. See skeleton-loading.md.
Server actionsactions/, one per file, suffix actionIn modules/<module>/actions/; file and function names end with action. See architecture.md.

Skeleton loading

Skeleton loading is an Achra pattern for loading states. Use it for route loading (loading.tsx), Suspense fallbacks, or any placeholder that should match the final layout to avoid shift.

Workflow: Locate the target UI → create a sibling {component-name}-skeleton.tsx → mirror structure and replace content with Skeleton elements sized to match → remove interactivity and data logic → validate layout parity and contrast.

Quick checklist:

  • Mirror layout containers and responsive classes (sm:, md:, etc.).
  • Replace text with Skeleton using line-height-derived heights; for multi-line with gap-1, subtract 2px per line to prevent layout shift.
  • Remove buttons, links, state, effects, and data fetching.
  • Use bg-border on skeletons inside bg-accent, bg-muted, or bg-secondary.
  • Reuse existing skeleton subcomponents when available.

Required import: import { Skeleton } from '@/shared/components/ui/skeleton'

Full rules, sizing, contrast, and accessibility: skeleton-loading.md. Patterns and examples: skeleton-loading-examples.md.

References

Full documentation:

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

github-tools

Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.

Archived SourceRecently Updated
Coding

openclaw-version-monitor

监控 OpenClaw GitHub 版本更新,获取最新版本发布说明,翻译成中文, 并推送到 Telegram 和 Feishu。用于:(1) 定时检查版本更新 (2) 推送版本更新通知 (3) 生成中文版发布说明

Archived SourceRecently Updated
Coding

ask-claude

Delegate a task to Claude Code CLI and immediately report the result back in chat. Supports persistent sessions with full context memory. Safe execution: no data exfiltration, no external calls, file operations confined to workspace. Use when the user asks to run Claude, delegate a coding task, continue a previous Claude session, or any task benefiting from Claude Code's tools (file editing, code analysis, bash, etc.).

Archived SourceRecently Updated
Coding

ai-dating

This skill enables dating and matchmaking workflows. Use it when a user asks to make friends, find a partner, run matchmaking, or provide dating preferences/profile updates. The skill should execute `dating-cli` commands to complete profile setup, task creation/update, match checking, contact reveal, and review.

Archived SourceRecently Updated