coffee-staff-management

Coffee Staff Management - Admin Dashboard for a coffee shop. Focus: Backend (.NET, EF Core, MediatR), Frontend (React/TypeScript, Vite), PostgreSQL schema (csm_db).

16 stars

Best use case

coffee-staff-management is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Coffee Staff Management - Admin Dashboard for a coffee shop. Focus: Backend (.NET, EF Core, MediatR), Frontend (React/TypeScript, Vite), PostgreSQL schema (csm_db).

Teams using coffee-staff-management should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/coffee-staff-management/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/development/coffee-staff-management/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/coffee-staff-management/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How coffee-staff-management Compares

Feature / Agentcoffee-staff-managementStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Coffee Staff Management - Admin Dashboard for a coffee shop. Focus: Backend (.NET, EF Core, MediatR), Frontend (React/TypeScript, Vite), PostgreSQL schema (csm_db).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Coffee Staff Management — Project Documentation

## 1. Project Overview
**Coffee Staff Management (CSM)** is an Admin Dashboard designed to manage employees, schedules, attendance, payroll, and revenue for a coffee shop.
- **Tech Stack**:
    - **Backend**: .NET 10 (Web API), Entity Framework Core (PostgreSQL), MediatR (CQRS).
    - **Frontend**: React (Vite), TypeScript, TailwindCSS (assumed), ShadCN (assumed).
    - **Database**: PostgreSQL (`csm_db`).

## 2. Core Workflows

### 2.1 Authentication & Dashboard
- **Actors**: Admin (Manager).
- **Flow**: Admin logs in via `username`/`password` -> Dashboard.
- **Dashboard**: Displays general stats (Overview). Includes Sidebar/Header for navigation.

### 2.2 Employee Management (`Employees`)
- **View**: List of employees (#, Code, Name, Phone, CID, Gender, Salaries, DOB, HireDate, Status).
- **Actions**: Search, Add, Edit, Delete (Soft delete? Status toggle?).

### 2.3 Position & Shift Management (`Positions`, `Shifts`)
- **Structure**: Employees can have multiple roles, but system manages Roles -> Shifts.
- **View**: List of Positions (Name, Shift Count, Status).
    - **Expand**: Show specific Shifts for that position (Name, Start/End Time).
- **Actions**: Manage Positions and their Shifts.

### 2.4 Scheduling (`Schedules`, `ScheduleRequests`)
- **Employee View (Mobile/Public Page)**:
    - Login via Phone Number.
    - View weekly table -> Register for shifts (optional Note).
    - Submit -> Creates `ScheduleRequest` (status: `pending`).
- **Admin View**:
    - View all requests.
    - **Action**: Approve/Reject requests.
    - **Result**: Approved requests become `Schedule` records.
    - **Calendar**: View final weekly schedule.

### 2.5 Attendance (`Attendance`)
- **Employee View**:
    - Login via Phone Number -> Select Position -> "Check In" / "Check Out".
    - System records time.
- **Admin View**:
    - View attendance records (Status, Check-in/out times, Late/Early notes).
    - **Data**: Links `Attendance` -> `Schedule` -> `Employee`.

### 2.6 Payroll (`Payrolls`, `PayrollDetails`)
- **Flow**: Admin Selects Month/Year & Employee -> System calculates Salary.
- **Calculation**:
    - Based on `Attendance` (Total Hours * Role Salary).
    - +/- `Rewards/Penalties`.
    - **Final**: Save to `Payrolls` table.

### 2.7 Revenue & Expenses (`Revenues`, `Transactions`)
- **Employee View (End of Shift)**:
    - Login via Phone -> Input Revenue (Cash, Bank, Expenses during shift).
    - System calculates Deviation (Expected vs Actual).
- **Admin View**:
    - View Daily/Monthly Revenue reports.
    - Manage `Transactions` (Income/Expense).

## 3. Database Schema (PostgreSQL)

### Tables
- **`admin`**: System administrators.
- **`employees`**: Staff details. `status` (bool).
- **`positions`**: Job roles.
- **`shifts`**: Specific work times for positions.
- **`schedule_requests`**: Staff registration for shifts. `status` ('pending', 'approved', 'rejected').
- **`schedules`**: Official assigned shifts.
- **`attendance`**: Actual work logs. Links to `schedules`.
- **`reward_penalty_types`**: Config for bonus/fines.
- **`rewards_penalties`**: Applied records.
- **`payrolls`**: Monthly efficiency summaries.
- **`payroll_details`**: Breakdown by attendance/shift.
- **`revenues`**: Daily/Shift revenue reports.
- **`transactions`**: Income/Expense records.
- **`activities`**: System audit log.

## 4. Current Implementation Status (Backend)
- **Architecture**: Clean Architecture (Domain, Application, Infrastructure, API).
- **Entities**: Synchronized with PostgreSQL Schema.
- **Features**:
    - [x] Employees (CRUD, Soft Delete).
    - [x] Positions/Shifts (CRUD, Status field standardized).
    - [x] Schedules (Request -> Approve cycle).
    - [x] Attendance (Check-in/out).
    - [x] Payroll (Weighted calculation, Rewards/Penalties).
    - [x] Revenue/Transactions (Expense-aware Net, Deviation logic).

## 5. Project Roadmap (Completed)
1.  **Database**: Fully synchronized and optimized.
2.  **Staff Portal**: Mobile-first portal with phone verification completed.
3.  **UI/UX**: Comprehensive Teal/Cyan standardization achieved across all pages.
4.  **Financials**: Automated payroll and revenue tracking fully implemented.

Related Skills

memory-management

16
from diegosouzapw/awesome-omni-skill

Guide for managing Claude Code memory effectively. Use when setting up project memory, optimizing CLAUDE.md files, configuring rules directories, or establishing cross-session knowledge patterns. Covers memory hierarchy, best practices, and context optimization.

Library Management

16
from diegosouzapw/awesome-omni-skill

User library, favorites, and reading progress

heir-sync-management

16
from diegosouzapw/awesome-omni-skill

Master-Heir synchronization, contamination prevention, and promotion workflows

file-management-rules

16
from diegosouzapw/awesome-omni-skill

Specifies file management guidelines, including including full file paths as comments, updating project structure in AI.MD, and maintaining package.json. This rule ensures organized and well-documente

database-management

16
from diegosouzapw/awesome-omni-skill

Database schema design, migrations, query optimization, and ORM best practices. Use for database setup, performance tuning, and data modeling.

Bankr x402 SDK - Job Management

16
from diegosouzapw/awesome-omni-skill

This skill should be used when the user asks about "job status", "check if request completed", "cancel request", "why is my request taking so long", "poll for result", "batch requests", "retry failed request", "request timeout", "async operations", "job lifecycle", "manual polling", or needs advanced control over SDK async operations, manual job polling, batch processing, retry logic, or job cancellation.

angular-state-management

16
from diegosouzapw/awesome-omni-skill

Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.

adr-management

16
from diegosouzapw/awesome-omni-skill

Create and manage Architecture Decision Records (ADRs). Use when documenting technology choices, design decisions, or architectural changes that need to be tracked over time. This is the CANONICAL ADR skill - all ADR-related work should use this skill.

adhd-task-management

16
from diegosouzapw/awesome-omni-skill

ADHD-optimized task tracking and intervention system. Use when tracking tasks, detecting context switches, providing accountability interventions, or managing ADHD-specific productivity patterns for Ariel Shapira.

access-management

16
from diegosouzapw/awesome-omni-skill

RBAC/ABAC implementation patterns, least privilege access, row-level security, column masking, and access review workflows.

skills-management

16
from diegosouzapw/awesome-omni-skill

Search, find, discover, install, remove, update, review, list, and move skills for AI coding agents. Use when user asks "find a skill for X", "search for a skill", "is there a skill for X", "install skill", "remove skill", "update skills", "list skills", "review skill quality", "move skill", "check for updates", or "how do I do X" where X might have an existing skill. This is THE tool for skill discovery and ecosystem search.

risk-management

16
from diegosouzapw/awesome-omni-skill

Manages financial risks through quantitative analysis, modeling, and mitigation strategies.