Fumadocs on TanStack Start

1. INTRODUCTION

This document is the operational guide for Freelancers and External Partners. It defines the rules of engagement, ensuring that your collaboration with Moustachir Com is smooth, productive, and aligned with our quality standards.

2. ROLES & EXPECTATIONS

2.1 The Freelancer's Role

You are hired as a specialist. We expect:

Autonomy: Ability to execute tasks with minimal hand-holding once requirements are clear.
Expertise: Bringing best practices from your domain (Dev, Design, QA, etc.).
Professionalism: Adhering to deadlines and communication protocols.

2.2 Communication Channels

Technical & Project Queries: Direct these to the IT Projects Manager or Team Lead via Discord.
Commercial & Contract Queries: Direct these to the IT Projects Manager.
- Strict Rule: You are not authorized to discuss project scope, timelines, or costs directly with the Client or the Commercial Team unless explicitly invited by the PM. All commercial alignment happens through the PM.

3. ONBOARDING & ACCESS

3.1 The Onboarding Checklist

Before starting work, you must complete the following:

Legal: Sign the Service Agreement and NDA.
Protocol: Read and acknowledge the General IT Protocol, this External Protocol, and your specific Role Protocol (Engineering or UI/UX).
Access:
- Discord: Join the server and introduce yourself in your project channel.
- Notion: Accept the invite to your specific project board.
- GitHub/Figma: Accept invites to the specific repositories/files you are assigned to.

3.2 Access Limitations

Principle of Least Privilege: You will only have access to the resources necessary for your specific task.
No Production Access: Freelancers generally do not have direct write access to production environments or the main branch.

4. WORKFLOWS & DELIVERABLES

4.1 Task Management (Notion)

Real-Time Updates: You must move your cards in Notion as you progress (To Do -> In Progress -> Review).
Comments: Use card comments to ask clarifying questions about specific tasks.
Weekly Check-in: Ensure your board is 100% accurate before the weekly review cycle.

4.2 Technical Guidelines

For detailed technical instructions, please refer to the role-based protocols. However, note the specific restrictions for external partners below:

For Developers

Refer to the General Engineering Protocol for shared standards (Git Flow, Code Quality). For role-specific onboarding and workflows, see: Frontend, Backend, Mobile, or AI/ML.

Development Phase Access: During active development, you will have direct push access to dev and staging branches for the repositories assigned to you.
Post-Development Phase: After the development phase concludes, access switches to Pull Request-based workflow only.
Production Restriction: You are strictly prohibited from pushing directly to main (Production) at any time.
Deployment: You do not have deployment rights to Production unless explicitly invited by the PM.

For Designers

Refer to the UI/UX Protocol for the standard Design Process.

Restriction: Do not modify the Master Design System library without explicit approval from the UI/UX Lead.

4.3 Reporting

Daily Updates: A quick message in your Discord project channel is appreciated (e.g., "Working on X today").
Blockers: Report blockers immediately. Do not wait for the next meeting. Tag the PM or Team Lead.

5. PERFORMANCE & EVALUATION

We value long-term relationships. Successful collaborations lead to repeat business.

Quality: Delivering bug-free, well-structured code/design.
Reliability: Meeting deadlines and communicating delays in advance.
Process Adherence: Following the Git flow, Notion updates, and communication rules defined in these protocols.

External IT Protocol