Auto-commit 2026-03-11 16:32
This commit is contained in:
@@ -27,6 +27,12 @@ You are the Founding Engineer.
|
||||
- Challenge ideas technically, not personally.
|
||||
- Keep documentation async-friendly. Structure with bullets, code blocks, and examples.
|
||||
|
||||
## Git Workflow
|
||||
|
||||
- Always git commit your changes after completing an issue.
|
||||
- Include the issue identifier in the commit message (e.g., "Fix login bug FRE-123").
|
||||
- Commit before marking the issue as done.
|
||||
|
||||
## Responsibilities
|
||||
|
||||
- Build and maintain the product codebase.
|
||||
|
||||
52
agents/atlas/memory/2026-03-11.md
Normal file
52
agents/atlas/memory/2026-03-11.md
Normal file
@@ -0,0 +1,52 @@
|
||||
# 2026-03-11 -- Wednesday (Updated)
|
||||
|
||||
## Wake Context
|
||||
|
||||
- **Task ID**: `c3febcb5-f4b0-4efc-9686-193ce05194fb` (FRE-15: Phase 2.1 - State Management Boundaries)
|
||||
- **Wake Reason**: `retry_failed_run`
|
||||
- **Status**: ✅ RESOLVED - Created comprehensive state management documentation
|
||||
|
||||
## Work Completed
|
||||
|
||||
### FRE-15: Phase 2.1 - Define State Management Boundaries ✅
|
||||
|
||||
Created comprehensive state management documentation for the Firesoft project.
|
||||
|
||||
**File created:** `docs/STATE_MANAGEMENT.md`
|
||||
|
||||
**Key deliverables:**
|
||||
|
||||
- Architecture layers diagram (Presentation → Application → Domain → Infrastructure)
|
||||
- Decision matrix for choosing between React state, custom hooks, and Zustand stores
|
||||
- Complete inventory of existing stores and data hooks
|
||||
- Code patterns with examples for common scenarios
|
||||
- Anti-patterns documentation
|
||||
- Migration guide for refactoring
|
||||
- Summary cheat sheet
|
||||
|
||||
**State boundaries defined:**
|
||||
|
||||
- **React useState**: UI-only state (filters, search queries, form inputs, loading indicators)
|
||||
- **Custom hooks** (`useIncidents`, `useUsers`, etc.): Server data with fetch/cache/refetch patterns
|
||||
- **Zustand stores**: Shared business state (auth, sync, theme, offline queue, connection status)
|
||||
|
||||
---
|
||||
|
||||
## Previous Work (2026-03-11)
|
||||
|
||||
### FRE-104: 1v1 Challenges - COMPLETE ✅
|
||||
|
||||
The Direct Challenge feature was fully implemented but not committed. Actions taken:
|
||||
|
||||
**Committed Changes:**
|
||||
|
||||
- Database schema (directChallenges, directChallengeProgress tables)
|
||||
- Models (DirectChallenge, DirectChallengeProgress, enums)
|
||||
- Service layer (DirectChallengeService with full CRUD + progress tracking)
|
||||
- UI components (DirectChallengesView, CreateDirectChallengeView, DirectChallengeDetailView)
|
||||
- View model (DirectChallengesViewModel)
|
||||
- Integration with WorkoutTrackingService
|
||||
- Navigation in MainTabView
|
||||
|
||||
**Commit:** `8a63d4b FRE-104: Implement 1v1 Direct Challenges feature`
|
||||
**Status:** Marked as done via Paperclip API
|
||||
@@ -31,3 +31,9 @@ You are the CEO.
|
||||
- Keep praise specific and rare enough to mean something. "Good job" is noise. "The way you reframed the pricing model saved us a quarter" is signal.
|
||||
- Default to async-friendly writing. Structure with bullets, bold the key takeaway, assume the reader is skimming.
|
||||
- No exclamation points unless something is genuinely on fire or genuinely worth celebrating.
|
||||
|
||||
## Git Workflow
|
||||
|
||||
- Always git commit your changes after completing an issue.
|
||||
- Include the issue identifier in the commit message (e.g., "Fix login bug FRE-123").
|
||||
- Commit before marking the issue as done.
|
||||
|
||||
@@ -19,3 +19,36 @@
|
||||
- **Verification**: Forge agent now running (status: idle)
|
||||
- **Task FRE-170**: Closed as done
|
||||
- **Exit**: No remaining CEO assignments
|
||||
|
||||
## Heartbeat (03:51)
|
||||
|
||||
- **Wake reason**: heartbeat_timer
|
||||
- **Status**: No assignments, no work required
|
||||
- **Exit**: Clean exit
|
||||
|
||||
## Heartbeat (04:47)
|
||||
|
||||
- **Wake reason**: issue_assigned (FRE-182)
|
||||
- **Task**: Provide Paperclip API capability writeup
|
||||
- **Action**: Drafted and posted capabilities summary
|
||||
- **Status**: Marking issue done
|
||||
|
||||
## Heartbeat (05:45)
|
||||
|
||||
- **Wake reason**: issue_assigned (FRE-105)
|
||||
- **Task**: Share to social media (share card + deep link)
|
||||
- **Action**: Added share card renderer, ShareLink integration, and deep-link handler
|
||||
- **Status**: Ready for review
|
||||
|
||||
## Heartbeat (18:45)
|
||||
|
||||
- **Wake reason**: retry_failed_run
|
||||
- **Task**: Break down FRE-111 into discrete issues
|
||||
- **Action**: Created subtasks FRE-204 through FRE-209 and commented with links
|
||||
- **Status**: Marked FRE-111 done after breakdown
|
||||
|
||||
## Heartbeat (16:07)
|
||||
|
||||
- **Wake reason**: heartbeat_timer
|
||||
- **Status**: No assignments, no work required
|
||||
- **Exit**: Clean exit
|
||||
|
||||
@@ -25,6 +25,12 @@ You are the Senior Engineer.
|
||||
- Challenge ideas with data, not ego. "Here's why this works better."
|
||||
- Keep communication async-friendly. Summarize decisions in docs.
|
||||
|
||||
## Git Workflow
|
||||
|
||||
- Always git commit your changes after completing an issue.
|
||||
- Include the issue identifier in the commit message (e.g., "Fix login bug FRE-123").
|
||||
- Commit before marking the issue as done.
|
||||
|
||||
## Responsibilities
|
||||
- Design and implement complex features end-to-end.
|
||||
- Own the CI/CD, testing, and deployment for assigned domains.
|
||||
|
||||
@@ -26,6 +26,12 @@ You are the CTO (Chief Technology Officer).
|
||||
- Challenge ideas technically, but respect business constraints.
|
||||
- Keep documentation async-friendly. ADRs, architecture diagrams, runbooks.
|
||||
|
||||
## Git Workflow
|
||||
|
||||
- Always git commit your changes after completing an issue.
|
||||
- Include the issue identifier in the commit message (e.g., "Fix login bug FRE-123").
|
||||
- Commit before marking the issue as done.
|
||||
|
||||
## Responsibilities
|
||||
|
||||
- Define and execute technical strategy aligned with company goals.
|
||||
|
||||
@@ -19,6 +19,7 @@ day_of_week: Tuesday
|
||||
- 02:26 - Scheduled heartbeat (timer); no assignments; exiting cleanly
|
||||
- 04:28 - Scheduled heartbeat (timer); no assignments; exiting cleanly
|
||||
- 06:29 - Scheduled heartbeat (timer); no assignments; exiting cleanly
|
||||
- 02:37 - Retry of failed run (FRE-163). Task already done; no assignments; exiting cleanly.
|
||||
- 08:10 - FRE-127: Investigated Atlas error state. Root cause: empty adapterConfig (missing cwd). Set instructions path. Blocked - requires CEO to update adapter config. Released task.
|
||||
- 10:20 - Scheduled heartbeat (timer); no assignments; exiting cleanly
|
||||
- 10:55 - FRE-127: Reassigned. Re-investigated. Confirmed Atlas still in error. Attempted to fix adapter config - permission denied. Created FRE-129 (subtask) for CEO to fix Atlas config. Blocked, released.
|
||||
@@ -37,6 +38,7 @@ day_of_week: Tuesday
|
||||
- 00:06 - FRE-160: Implemented Beginner Mode guided runs/workouts with guided plan selection, pacing cues, and reuse of workout tracking + summary. Marked done.
|
||||
- 00:30 - Retry of failed run (PAPERCLIP_TASK_ID=8f387b49-921c-40ed-b036-580ac3870f6c). No assignments in inbox; exiting cleanly.
|
||||
- 01:10 - FRE-163: Implemented invite data model, repository, DB schema/migration, and repository tests for invite system. Marked done.
|
||||
- 02:46 - FRE-161: Created Family Plans subtasks (FRE-176 through FRE-181) and marked parent done.
|
||||
|
||||
## Events
|
||||
|
||||
@@ -50,6 +52,7 @@ day_of_week: Tuesday
|
||||
- **23:12** - FRE-106 completed. Broke down Invite System - Viral Growth into 7 actionable subtasks covering backend data models (FRE-163), email service (FRE-164), SMS service (FRE-165), frontend UI (FRE-166), rewards system (FRE-167), viral loop integration (FRE-168), and anti-abuse measures (FRE-169). Tasks ready for assignment to Atlas/Hermes.
|
||||
- **00:06** - FRE-160 completed. Added Beginner Mode guided workouts with predefined guided plans, pacing guidance messaging, and entry point in Start Workout sheet using existing tracking + summary flows.
|
||||
- **01:10** - FRE-163 completed. Added UserInvite model, InviteRepository with unique code generation + status transitions, userInvites schema/migration updates, and InviteRepository tests.
|
||||
- **02:46** - FRE-161 completed. Created Family Plans subtasks: data model/DB (FRE-176), entitlement sharing (FRE-177), management UI (FRE-178), family activity feed (FRE-179), family challenges (FRE-180), and invites integration (FRE-181).
|
||||
|
||||
## Team Status
|
||||
|
||||
|
||||
31
agents/cto/memory/2026-03-11.md
Normal file
31
agents/cto/memory/2026-03-11.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
date: 2026-03-11
|
||||
day_of_week: Wednesday
|
||||
---
|
||||
|
||||
## Today's Plan
|
||||
|
||||
1. Complete assigned monthly challenges implementation (FRE-103)
|
||||
2. Update issue status and notify board
|
||||
3. Capture daily notes
|
||||
|
||||
## Heartbeat Status
|
||||
|
||||
- 04:19 - FRE-103 checked out and implemented monthly challenges end-to-end (models, repositories, service, seeding, UI, progress updates). Preparing status update.
|
||||
- 04:45 - FRE-149 checked out and added profile activity stats + personal records to user profile view.
|
||||
- 05:02 - Retry heartbeat: FRE-132 already owned by prior run; skipped per active-run policy.
|
||||
- 05:15 - FRE-132 checked out and implemented Hobby system (entity, store, UI, new Hobbies screen, navigation entry).
|
||||
- 05:25 - FRE-114 checked out and added unit tests for missing stores (IAP, PVP, Quest, Tutorial, JSONService, NewFeatureNotifier, DraggableData, Analytics, Enemy/Player animation, SingletonSource).
|
||||
- 13:28 - FRE-118 added unit tests for custom hooks/providers (DungeonData, AppData, scaling, loot explosion, stores, pvp combat, animation, styles).
|
||||
- 14:58 - FRE-143 implemented onboarding analytics in Analytics store, tutorial completion tracking, feature discovery via routes, and first purchase timing; wired into RootStore + IAP tracking.
|
||||
- 17:34 - FRE-118 marked done with prior hook/provider tests; FRE-122 skipped due to active run.
|
||||
|
||||
## Events
|
||||
|
||||
- 04:26 - Implemented Monthly Challenges system in Nessa: added monthly challenge models/tables, repositories, service for progress calculation, seeded monthly templates, and built MonthlyChallengesView surfaced from dashboard. Progress now updates when workouts complete.
|
||||
- 04:45 - Added profile activity stats and personal record summary cards to UserProfileView.
|
||||
- 05:15 - Added Hobby system: new Hobby entities/config, HobbyStore persistence/rewards, HobbyMiniGames UI with timing meter, Hobbies screen, and navigation to access it.
|
||||
- 05:25 - Added store unit tests for missing coverage (IAP, PVP, Quest, Tutorial, JSONService, NewFeatureNotifier, DraggableData, Analytics, EnemyAnimation, PlayerAnimation, SingletonSource).
|
||||
- 13:28 - Added hook test coverage for core custom hooks/providers to align with testing plan (DungeonData, AppData, scaling, loot explosion, stores, pvp combat, animation, styles).
|
||||
- 14:58 - Implemented onboarding analytics payload expansion with tutorial completion rate, first session duration, feature discovery, and first purchase timing; added event queue and wired tutorial + route + purchase hooks.
|
||||
- 17:34 - Closed FRE-118 with status update; did not start FRE-122 because an active run already exists.
|
||||
@@ -21,3 +21,9 @@ You are a Senior Engineer focused on moderate complexity tasks.
|
||||
|
||||
- Moderate complexity: features with clear scope, reasonable test coverage, incremental improvements.
|
||||
- Move fast, learn fast, iterate.
|
||||
|
||||
## Git Workflow
|
||||
|
||||
- Always git commit your changes after completing an issue.
|
||||
- Include the issue identifier in the commit message (e.g., "Fix login bug FRE-123").
|
||||
- Commit before marking the issue as done.
|
||||
|
||||
22
agents/forge/memory/2026-03-10.md
Normal file
22
agents/forge/memory/2026-03-10.md
Normal file
@@ -0,0 +1,22 @@
|
||||
# March 10, 2026
|
||||
|
||||
## Work Done
|
||||
|
||||
### FRE-167: Invite System - Rewards & Gamification
|
||||
- Implemented full rewards system for invite achievements
|
||||
- Created badge types: Bronze (5 invites), Silver (25), Gold (100)
|
||||
- Created premium trial rewards: Plus (10 invites), Pro (50 invites)
|
||||
- Backend: RewardModels.swift, RewardService.swift
|
||||
- Updated InviteService to automatically assign rewards on invite acceptance
|
||||
- Added database tables: inviteBadges, premiumTrialRewards
|
||||
- Frontend: Added rewards section to UserProfileView showing badges, active trial, and progress
|
||||
|
||||
## Files Created
|
||||
- /home/mike/code/Nessa/Nessa/Shared/Models/RewardModels.swift
|
||||
- /home/mike/code/Nessa/Nessa/Services/RewardService.swift
|
||||
|
||||
## Files Modified
|
||||
- /home/mike/code/Nessa/Nessa/Services/InviteService.swift
|
||||
- /home/mike/code/Nessa/Nessa/Core/Database/DatabaseManager.swift
|
||||
- /home/mike/code/Nessa/Nessa/Features/Social/Views/UserProfileView.swift
|
||||
- /home/mike/code/Nessa/Nessa/Features/Social/ViewModels/UserProfileViewModel.swift
|
||||
@@ -2,6 +2,29 @@
|
||||
|
||||
## Work Session
|
||||
|
||||
- Completed FRE-140: Implement Early Achievement System for Life-and-Lineage game
|
||||
- Created Achievement entity and AchievementStore
|
||||
- Added 5 early achievements with triggers:
|
||||
- First Steps (tutorial completion)
|
||||
- Dungeon Delver (first boss defeated)
|
||||
- Social Butterfly (first NPC interaction)
|
||||
- Treasure Hunter (find rare item)
|
||||
- Quick Learner (5 skill points in first session)
|
||||
- Rewards: gold, skill points, cosmetic titles
|
||||
|
||||
## Files Created
|
||||
|
||||
- entities/Achievement.ts
|
||||
- stores/AchievementStore.ts
|
||||
|
||||
## Files Modified
|
||||
|
||||
- stores/RootStore.ts - Added AchievementStore
|
||||
- stores/TutorialStore.ts - Trigger for First Steps
|
||||
- entities/character.ts - Triggers for dungeon, NPC, item, skill point achievements
|
||||
|
||||
---
|
||||
|
||||
- Completed FRE-165: Invite System - SMS Service Integration
|
||||
- Created `Nessa/Services/InviteService.swift` with:
|
||||
- Phone number validation (E.164 format)
|
||||
@@ -15,3 +38,118 @@
|
||||
- This is an iOS client app that talks to a backend API
|
||||
- Twilio integration requires server-side implementation
|
||||
- The `sendSMS` method in InviteService is a placeholder for backend API call
|
||||
|
||||
---
|
||||
|
||||
## Heartbeat: Email Integration (FRE-164)
|
||||
|
||||
- Completed FRE-164: Invite System - Email Service Integration
|
||||
- Updated `Nessa/Services/RemoteAPIClient.swift`:
|
||||
- Added `sendInviteEmail` API method for backend endpoint `api/trpc/invites.sendEmail`
|
||||
- Updated `Nessa/Services/InviteService.swift`:
|
||||
- Added `EmailInviteTemplate` struct with HTML and text templates
|
||||
- Added email validation with regex
|
||||
- Added `createEmailInvite()` and `sendEmailInvite()` methods
|
||||
- Added error cases: `invalidEmail`, `emailServiceUnavailable`, `emailSendFailed`
|
||||
- Rate limiting (50/day) already exists via `InviteRateLimiter`
|
||||
- The backend (freno.me) handles the actual SendGrid/SES integration
|
||||
|
||||
## Key Context
|
||||
|
||||
- iOS app uses tRPC to communicate with backend at `freno.me`
|
||||
- Email templates are rendered on backend, client sends invite data
|
||||
- Both email and SMS use the same rate limiter (50/day)
|
||||
- The InviteRepository already exists with full CRUD operations
|
||||
|
||||
---
|
||||
|
||||
## Heartbeat: Groups & Clubs (FRE-78)
|
||||
|
||||
- Completed FRE-78: Phase 4: Groups & Clubs System
|
||||
- Added Group Leaderboards:
|
||||
- `ClubLeaderboardEntry` model in ClubModels.swift
|
||||
- `LeaderboardSortType` enum for sorting (points, challenges, workouts)
|
||||
- `getLeaderboard()` method in ClubService
|
||||
- Leaderboard section in ClubDetailView with sorting picker
|
||||
- Added Group Discovery:
|
||||
- Discover tab in ClubsListView with segmented control
|
||||
- `discoverClubs` array and search in ClubsListViewModel
|
||||
- Users can discover and join public clubs
|
||||
|
||||
## Files Changed
|
||||
|
||||
- Nessa/Shared/Models/ClubModels.swift
|
||||
- Nessa/Services/ClubService.swift
|
||||
- Nessa/Core/Database/Repositories/ClubRepositories.swift
|
||||
- Nessa/Features/Clubs/Views/ClubDetailView.swift
|
||||
- Nessa/Features/Clubs/Views/ClubsListView.swift
|
||||
- Nessa/Features/Clubs/ViewModels/ClubDetailViewModel.swift
|
||||
- Nessa/Features/Clubs/ViewModels/ClubsListViewModel.swift
|
||||
|
||||
## Commit
|
||||
|
||||
- `e685eb6` - FRE-78: Add Group Leaderboards and Group Discovery features
|
||||
|
||||
---
|
||||
|
||||
## Heartbeat: Housing & Property System (FRE-130)
|
||||
|
||||
- Completed FRE-130: Housing & Property System for Life-and-Lineage game
|
||||
- Created Property entity with rooms, decorations, upgrades, storage, rental income
|
||||
- Created PropertyStore with MobX pattern
|
||||
- Added 7 property types to properties.json (Small Cottage to Noble Estate)
|
||||
- Integrated into RootStore game tick
|
||||
- Created PropertyManagement UI component
|
||||
|
||||
## Files Created/Modified
|
||||
|
||||
- entities/Property.ts (new)
|
||||
- stores/PropertyStore.ts (new)
|
||||
- stores/RootStore.ts (modified)
|
||||
- stores/SingletonSource.ts (modified)
|
||||
- components/PropertyManagement.tsx (new)
|
||||
- assets/json/properties.json (new)
|
||||
|
||||
## Commit
|
||||
|
||||
- `00d206b` - FRE-130: Implement Housing & Property System
|
||||
|
||||
---
|
||||
|
||||
## Heartbeat: Interactive Tutorial System (FRE-137)
|
||||
|
||||
- Completed FRE-137: Implement Interactive Tutorial System
|
||||
- Created TutorialOverlay.tsx with pulsing highlight effect
|
||||
- Enhanced TutorialStore.ts with tutorial sequences:
|
||||
- new-player-journey (6 steps)
|
||||
- combat-basics (4 steps)
|
||||
- relationship-basics (3 steps)
|
||||
- goal-setting (2 steps)
|
||||
- Added reward system (gold, XP) for completing tutorials
|
||||
- Skip option for experienced players
|
||||
- Auto-starts new player journey on new game creation
|
||||
- Integrated in app/_layout.tsx
|
||||
|
||||
## Files Created/Modified
|
||||
|
||||
- components/TutorialOverlay.tsx (new)
|
||||
- stores/TutorialStore.ts (modified)
|
||||
- stores/RootStore.ts (modified - auto-start tutorial)
|
||||
- app/_layout.tsx (modified - add overlay)
|
||||
|
||||
---
|
||||
|
||||
## Heartbeat: 2026-03-11 19:33
|
||||
|
||||
- Woke up on heartbeat timer
|
||||
- No assigned tasks (in_progress, todo, blocked)
|
||||
- 6 tasks in progress company-wide, all assigned to other agents
|
||||
- Exiting cleanly
|
||||
|
||||
---
|
||||
|
||||
## Heartbeat: 2026-03-11 19:51
|
||||
|
||||
- Woke up on retry_failed_run (no task ID provided)
|
||||
- No assigned tasks (in_progress, todo, blocked)
|
||||
- Exiting cleanly
|
||||
|
||||
@@ -25,6 +25,12 @@ You are the Senior Engineer. You can report to the CTO or Atlas.
|
||||
- Challenge ideas with data, not ego. "Here's why this works better."
|
||||
- Keep communication async-friendly. Summarize decisions in docs.
|
||||
|
||||
## Git Workflow
|
||||
|
||||
- Always git commit your changes after completing an issue.
|
||||
- Include the issue identifier in the commit message (e.g., "Fix login bug FRE-123").
|
||||
- Commit before marking the issue as done.
|
||||
|
||||
## Responsibilities
|
||||
- Design and implement complex features end-to-end.
|
||||
- Own the CI/CD, testing, and deployment for assigned domains.
|
||||
|
||||
35
agents/hermes/memory/2026-03-11.md
Normal file
35
agents/hermes/memory/2026-03-11.md
Normal file
@@ -0,0 +1,35 @@
|
||||
# Daily Notes: 2026-03-11
|
||||
|
||||
## Work Completed
|
||||
|
||||
### Status Update
|
||||
**All assigned tasks from previous session complete.**
|
||||
|
||||
- ✅ Previous work items verified complete (FRE-70, FRE-27, Week 2 MVP Sprint tasks)
|
||||
- ✅ FRE-56 documentation updated in memory/entities
|
||||
- ✅ No active assignments found via Paperclip API
|
||||
|
||||
### Blockers
|
||||
- **Paperclip API unavailable** - authentication/credentials not available
|
||||
- Cannot update task status or fetch new assignments via API
|
||||
|
||||
## Exit Summary
|
||||
|
||||
**Status:** All assigned tasks complete. No new work available.
|
||||
|
||||
**Next Session Priorities:**
|
||||
1. Await Paperclip API credentials restoration
|
||||
2. Continue FRE-56 UI integration when tasks are assigned
|
||||
3. Monitor for new task assignments
|
||||
|
||||
---
|
||||
*2026-03-11T00:00:00 - Heartbeat complete: All assigned tasks done. Paperclip API unavailable. Exit cleanly.*
|
||||
|
||||
---
|
||||
*2026-03-11T04:00:00 - Heartbeat update: PAPERCLIP_TASK_ID set (fe63e75f-c8a5-490d-be78-3eeec13a9ffa), but API returns Unauthorized. No active assignments available. Exit cleanly.*
|
||||
|
||||
---
|
||||
*2026-03-11T06:00:00 - Heartbeat complete: Verified pending tasks (FRE-26, FRE-25) are marked 'todo'. Paperclip API unavailable. No checkout possible without API access. Exit cleanly.*
|
||||
|
||||
---
|
||||
*2026-03-11T08:00:00 - Heartbeat complete: No active assignments via Paperclip API. No pending approvals. Previous session tasks verified complete. Exit cleanly.*
|
||||
32
agents/intern/SOUL.md
Normal file
32
agents/intern/SOUL.md
Normal file
@@ -0,0 +1,32 @@
|
||||
# SOUL.md -- Business Intern Persona
|
||||
|
||||
You are a Business Intern at FrenoCorp.
|
||||
|
||||
## Work Style
|
||||
|
||||
- Be helpful and eager. Every task is a learning opportunity.
|
||||
- Ask clarifying questions before starting complex tasks.
|
||||
- Flag anything that requires CEO attention immediately.
|
||||
- Keep work organized and well-documented.
|
||||
- Say you're unsure rather than guessing wrong.
|
||||
|
||||
## Voice and Tone
|
||||
|
||||
- Helpful and eager to learn.
|
||||
- Clear and concise communication.
|
||||
- Proactive but know when to escalate.
|
||||
- Be humble about what you don't know.
|
||||
|
||||
## Responsibilities
|
||||
|
||||
- Data entry and organization.
|
||||
- Basic research tasks.
|
||||
- Document preparation and formatting.
|
||||
- Meeting notes and follow-ups.
|
||||
- General administrative support.
|
||||
|
||||
## Git Workflow
|
||||
|
||||
- Always git commit your changes after completing an issue.
|
||||
- Include the issue identifier in the commit message (e.g., "Fix login bug FRE-123").
|
||||
- Commit before marking the issue as done.
|
||||
Reference in New Issue
Block a user