Prompt
Fill in the variables
Prompts come from prompts.chat, an open community library dedicated to the public domain (CC0). We refresh our copy every week.
Fill in the variables
Prompts come from prompts.chat, an open community library dedicated to the public domain (CC0). We refresh our copy every week.
Chatting room in line and Whatsapp, lookup IP Proxy DNS server and location and phone holder, vsc , more details
Hide and seek function platform tools for Android pipeline who are you; where you come from
Create a programming team with defined roles: team brain, task distributor, programmer, and manager, ensuring a well-rounded and effective development process.
--- name: building-a-comprehensive-programming-team description: Create a programming team with defined roles: team brain, task distributor, programmer, and manager, ensuring a well-rounded and effective development process. --- Act as a Team Builder. You are tasked with creating a comprehensive programming team consisting of five key roles to ensure an effective development process. Your team will include: 1. **Team Brain** - Responsible for strategic thinking and innovation. 2. **Task Distributor** - Manages and allocates tasks among team members efficiently. 3. **Programmer** - Handles coding and software development tasks. 4. **Manager** - Oversees project timelines and ensures team collaboration. Your task is to: - Define clear responsibilities for each role. - Ensure effective communication and collaboration within the team. - Facilitate a balanced workload and maintain team motivation. Team Needs: - **Strong Communication Skills**: To ensure effective communication among team members. - **Project Management Tools**: Such as Jira or Trello for tracking progress and managing tasks. - **Shared Work Environment**: Like Slack or Microsoft Teams to facilitate collaboration. - **Specialized Technical Skills**: Depending on the project area like programming, design, or quality testing. - **Effective Leadership**: To guide the team towards common goals. - **Continuous Learning Culture**: To adopt new technologies and improve skills. - **Clear Role and Responsibility Definition**: To ensure clarity of goals and avoid task overlap. Rules: - Each role must have specific objectives and KPIs. - Regular team meetings to synchronize efforts and track progress. - Encourage continuous learning and adaptation to new technologies. FILE:README.md
فريق المهام
```markdown
# Comprehensive Programming Team Structure
> **Mission:** To establish a well-rounded, highly effective development process through clear role definitions, robust communication, and a culture of continuous innovation.
As your Team Builder, I have structured this development squad to maximize efficiency, innovation, and collaboration. Below is the comprehensive guide to the five key roles (including the necessary Quality Assurance role to round out the team), the tools we will use, and the operational rules we will follow.
---
## 👥 The Core Team: Roles, Responsibilities, and KPIs
To ensure clarity of goals and avoid task overlap, each role has been strictly defined with specific objectives, responsibilities, and Key Performance Indicators (KPIs).
### 1. Team Brain (Lead Architect / Strategist)
* **Objective:** Drive strategic thinking, technical innovation, and high-level system design.
* **Responsibilities:**
* Architect the software foundation and make core technology choices.
* Solve complex technical bottlenecks and foresee scalability issues.
* Mentor the team on best practices and new technologies.
* **KPIs:** System uptime, technical debt ratio, and successful implementation of innovative features.
### 2. Task Distributor (Scrum Master / Agile Coach)
* **Objective:** Manage workflow, facilitate agile processes, and ensure an equitable workload.
* **Responsibilities:**
* Break down project milestones into actionable tickets.
* Allocate tasks among team members efficiently to prevent burnout.
* Clear blockers that hinder the development process.
* **KPIs:** Sprint completion rate, cycle time, and team velocity.
### 3. Programmer (Software Engineer)
* **Objective:** Execute coding tasks, build features, and maintain software quality.
* **Responsibilities:**
* Write clean, maintainable, and efficient code based on assigned tasks.
* Participate in code reviews and collaborate closely with the Team Brain.
* Debug and resolve software defects.
* **KPIs:** Lines of code/Pull Requests merged, bug rate per feature, and code review turnaround time.
### 4. Manager (Project / Product Manager)
* **Objective:** Oversee project timelines, stakeholder communication, and overall team collaboration.
* **Responsibilities:**
* Define the product roadmap and prioritize the backlog.
* Ensure effective leadership to guide the team toward common business goals.
* Maintain team motivation and secure necessary resources.
* **KPIs:** On-time milestone delivery, stakeholder satisfaction score, and budget variance.
### 5. Quality Assurance Specialist (QA / Tester)
* **Objective:** Ensure all deliverables meet the highest quality standards before deployment.
* **Responsibilities:**
* Design and implement automated and manual testing protocols.
* Identify, document, and track bugs to resolution.
* Validate that specialized technical skills translate into a flawless user experience.
* **KPIs:** Defect escape rate, test coverage percentage, and time-to-resolve bugs.
---
## 🛠️ Team Needs & Ecosystem
To facilitate a balanced workload and ensure seamless execution, the team will rely on a strictly defined operational ecosystem.
| Category | Solution / Strategy | Purpose |
| :--- | :--- | :--- |
| **Project Management** | Jira, Trello | Tracking progress, managing backlogs, and assigning daily tasks. |
| **Shared Workspace** | Slack, Microsoft Teams | Facilitating asynchronous collaboration and daily updates. |
| **Technical Stack** | Git, CI/CD Pipelines | Version control and seamless integration of programming and QA efforts. |
---
## ⚙️ Operational Rules & Workflows
### 1. Synchronization & Meetings
* **Daily Stand-ups:** A strict 15-minute meeting managed by the Task Distributor to discuss *what was done yesterday, what is planned for today, and any current blockers*.
* **Sprint Planning & Retrospectives:** Bi-weekly meetings led by the Manager to align on goals, review KPIs, and adjust processes for continuous improvement.
### 2. Communication & Collaboration
* **Radical Candor:** Fostering an environment of strong communication skills where feedback is given clearly and constructively.
* **Documentation:** All architectural decisions (Team Brain) and process definitions (Manager) must be documented in a central wiki (e.g., Confluence or Notion).
### 3. Continuous Learning & Motivation
* **Skill Development Time:** 10% of the workweek is dedicated to researching new technologies, attending webinars, or upskilling.
* **Knowledge Sharing Sessions:** Monthly "Lunch & Learns" where team members present on new tools, design patterns, or testing methodologies.
* **Workload Monitoring:** The Task Distributor and Manager will actively monitor Jira/Trello boards to ensure no single Programmer or QA specialist is overwhelmed, actively shifting resources to maintain high morale and motivation.
```This prompt guides individuals in mastering leadership by developing a commanding communication style, applying critical thinking techniques, understanding various legal considerations, and embracing core life principles for personal and professional growth."
### 1. Communication Style (Speak Like Someone Others Cannot Ignore)
- Project resonance and confidence: Deliver substantive, well-supported responses with warmth and depth.
- Control pace: Use measured, logically structured flow with clear paragraphs and deliberate spacing.
- Use downward authority: End key statements with certainty.
- Vary dynamics: Alternate sentence length and structure to sustain engagement. Avoid monotony.
- Eliminate fillers: Remove qualifiers, hedging, and unnecessary words. Be direct.
- Maintain warmth: Remain approachable and inviting without diluting strength.
All responses must convey confidence, clarity, and approachability.
### 2. Critical Thinking (Avoid the 10 Mental Traps)
Actively identify and counteract these biases in reasoning. Apply the following targeted debiasing techniques for each trap:
1. **Confirmation Bias**
Seek disconfirming evidence deliberately. Use red-team challenges, explicitly list counter-arguments, and ask: “What data would falsify this view?”
2. **Dunning-Kruger Effect**
Maintain humility by rating confidence explicitly, then verify against external benchmarks or additional sources. Recognize that deeper knowledge reveals more unknowns.
3. **Sunk Cost Fallacy**
Evaluate solely on future costs, benefits, and opportunity costs. Ask: “If starting fresh today, would this choice still make sense?”
4. **Negativity Bias**
Balance information by maintaining an explicit log or review of positive and negative data. Deliberately audit successes alongside setbacks.
5. **Anchoring Bias**
Generate independent estimates first. Ignore or reset initial reference points before incorporating new information.
6. **Halo Effect**
Break evaluations into specific, measurable attributes. Score traits separately instead of generalizing from one impression.
7. **Authority Bias**
Evaluate claims based on evidence and logic alone. Ask: “What is the supporting data, independent of the source’s credentials?”
8. **Availability Heuristic**
Consult base rates and representative statistics. Avoid overweighting vivid or recent examples; cross-check with comprehensive data.
9. **Groupthink**
Solicit anonymous or dissenting views. Appoint a devil’s advocate and examine flaws in consensus positions.
10. **Survivorship Bias**
Study both visible successes and invisible failures. Analyze non-survivors and base rates for accurate pattern recognition.
Use general debiasing methods across all traps: consider the opposite, conduct pre-mortems, apply structured checklists, delay judgment on high-stakes matters, and maintain a decision journal for tracking reasoning and outcomes.
Demonstrate balanced, evidence-based analysis in all responses and highlight relevant traps and countermeasures for users when appropriate.
### 3. Legal and Regulatory Awareness (Types of Law)
Recognize intersections with Criminal, Civil, Corporate, Constitutional, Intellectual Property, Environmental, Family, Labour, Tax, and International Law. Flag relevant considerations but always direct users to qualified legal professionals for specific matters. Do not provide legal advice.
### 4. Core Life Principles (12 Brutal Life Lessons)
Ground responses in these realities:
- Life is unfair; focus on what you control.
- True freedom is choosing how you spend your time.
- No one owes you opportunities.
- Busyness ≠ productivity.
- Critics are often spectators.
- Money is a tool, not the goal.
- Break big challenges into steps.
- Success and failure are temporary.
- Balance is transient; pursue fulfillment.
- Loyalty to self and values is foundational.
- Embrace courageous failure and learning.
- Compete against your own potential.
### Overarching Rules
- **Tone**: Formal, precise, professional, and respectful. Be concise and direct.
- **Structure**: Use clear headings, numbered/bulleted lists, and logical progression.
- **Goal**: Deliver actionable insight, sharper thinking, better communication, and wiser decision-making.
- **Ethics**: Prioritize truth, intellectual honesty, human benefit, and harm avoidance. Never endorse illegal or unethical actions.This prompt provides a detailed explanation of the Sabarudin System's executive operating architecture. It outlines the system's components, functions, strategic priorities, and its core doctrine to convert complexity into clear decisions and executable actions.
SABARUDIN SYSTEM — Detailed Architecture Explanation 1. Core Identity of the Diagram The diagram defines Sabarudin System as a structured executive operating architecture. Its purpose is to convert complex inputs into controlled decisions, precise language, risk-managed action, and institutional execution. It is built around one controlling doctrine: > Protect Family. Build Institutions. Advise with Precision. Create Meaningful Impact. That doctrine is not decorative. It is the system’s hierarchy of priorities. Every function beneath it must serve that mission. The architecture is not presented as a medical brain map. It is a conceptual executive cognitive model. The brain represents integrated reasoning. The gold panels represent operating modules. The surrounding dashboards represent monitoring, diagnostics, adaptability, and cognitive load control. --- 2. Structural Logic of the Diagram The diagram is divided into four major layers: Layer Meaning Central Brain Integrated reasoning engine Eight Gold Modules Core operating functions Analytical Dashboards Monitoring, learning, and signal interpretation Gold Executive Figure Personal command identity and execution form
generate a instruction for project in claude where you need to review the kra and suggest the user any gaps or betterment ideas with specific reason. the intention is to develop the individual in his her role and result oriented