Browse All Prompts

Write clear user stories with testable acceptance criteria. Format: 'As a [persona], I want [functionality], so that [benefit].' Example: 'As a returning customer, I want to save my payment information, so that I can checkout faster on future purchases.' Acceptance criteria using Given-When-Then: Given I'm a logged-in user, When I reach checkout with previously saved payment methods, Then I should see my saved cards as options, And I can select one with a single click, And the form auto-fills payment details. Include edge cases: expired cards, declined payments, first-time users. Definition of Ready: story has clear acceptance criteria, designs attached, effort estimated, dependencies identified. Definition of Done: feature tested, documented, deployed, analytics tracking added.

Profile and optimize performance. Tools: 1. Chrome DevTools (Performance, Lighthouse). 2. React DevTools Profiler. 3. Node.js --prof and clinic.js. 4. Bundle analysis (webpack-bundle-analyzer). 5. Database query analysis (EXPLAIN). 6. APM tools (New Relic, DataDog). Focus on: render performance, bundle size, API latency, memory usage. Measure before optimizing. Profile in production-like environments.

Test API endpoints comprehensively. Approach: 1. Test full request/response cycle. 2. Use real database (test instance). 3. Setup/teardown for clean state. 4. Test authentication and authorization. 5. Validate response schemas. 6. Test error scenarios. 7. Performance testing. 8. Security testing. Use Supertest or similar. Run in CI/CD. Separate from unit tests. Mock external APIs.

Develop cohesive content strategy across multiple platforms and formats. Platform optimization: 1. Instagram: 1080×1080 square images, 9:16 stories, carousel posts for engagement. 2. LinkedIn: professional tone, 1200×628 link previews, native video performs 5x better. 3. TikTok: vertical 9:16 format, 15-60 seconds, trending audio integration. 4. YouTube: custom thumbnails, 16:9 aspect ratio, eye-catching titles under 60 characters. Content pillars (80/20 rule): 80% valuable content (educational, entertaining), 20% promotional. Editorial calendar: 1. Content themes by weekday (Monday motivation, Wednesday wisdom). 2. Seasonal campaigns: holiday content, industry events, product launches. 3. Content recycling: one core idea adapted for 5-7 different formats. Production workflow: 1. Batch creation: film multiple pieces in single session. 2. Template systems: consistent branding across platforms. 3. Approval process: stakeholder review, compliance checking. Analytics: engagement rates by platform, content type performance, optimal posting times analysis.

Scan for security vulnerabilities. Tools: 1. SAST (Snyk, SonarQube) for code analysis. 2. DAST for runtime scanning. 3. Dependency scanning (npm audit, Dependabot). 4. Secret detection (GitGuardian). 5. Container scanning. 6. Infrastructure as Code scanning. Integrate in CI/CD. Fix critical issues immediately. Use OWASP Top 10 as guide. Regular security reviews.

Use restorative circles to address classroom conflicts instead of punitive measures. Scenario: Two students had a verbal argument. Process: 1. Preparation: Meet with each student individually to hear their perspective. 2. The Circle: Bring both students, a facilitator (teacher/counselor), and possibly a trusted peer for each. 3. Opening: Use a talking piece to ensure one person speaks at a time. 4. Questions: 'What happened?' 'What were you thinking at the time?' 'Who has been affected?' 'What do you need to make things right?' 5. Agreement: Students collaboratively decide on a plan to repair the harm (e.g., apology, replacing a damaged item, working together on a task). 6. Follow-up: Check in with students the next day. Goal: focus on repairing relationships and learning from mistakes.

Build comprehensive E2E testing with Playwright. Test structure: 1. Page Object Model for maintainability. 2. Multi-browser testing (Chromium, Firefox, WebKit). 3. Parallel test execution. 4. Visual regression with screenshots. 5. Network mocking and interception. 6. Authentication state persistence. 7. Trace viewer for debugging. 8. CI/CD integration with GitHub Actions. Use fixtures for test data, implement retry logic, and generate HTML reports with test results.

Teach students to 'think about their thinking'. Strategies: 1. Pre-assessment: Before a unit, have students complete a 'What I Know, What I Want to Know' (KWL) chart. 2. The Muddiest Point: During a lesson, pause and ask students to write down the 'muddiest point'—what is least clear to them. 3. Exam Wrappers: After a test, have students analyze their performance. Ask: 'How did you study?' 'What types of questions did you miss?' 'What will you do differently next time?' 4. Reflective Journals: Prompt students to reflect on their learning process weekly. 'What strategy worked well for you this week?' 'Where did you get stuck?' Goal: move students from passive recipients to active managers of their own learning.

Leverage Valtio's proxy magic for state. Usage: 1. proxy() creates mutable state. 2. Direct property mutations. 3. snapshot() for immutable reads. 4. useSnapshot hook in React. 5. subscribe() for listeners. 6. Nested objects auto-tracked. 7. Derive computed values. 8. Works outside React. Simple mental model: mutate state directly, components auto-update. Use with class instances for OOP patterns.

Leverage AI to provide faster, more personalized feedback on student writing. Tools: Writable, Turnitin Feedback Studio, ChatGPT. Workflow: 1. Students submit essays to an AI-powered platform. 2. The AI provides instant feedback on grammar, spelling, sentence structure, and style. 3. The AI can also check for plagiarism and assess against a rubric. 4. Teacher reviews the AI's comments, adds higher-level feedback on argumentation and critical thinking, and adjusts the AI-generated score. 5. Students use the combined feedback to revise their work. Benefits: saves teacher time on low-level corrections, provides immediate feedback to students, allows teachers to focus on more substantive comments. Ethical consideration: teach students how to use AI as a tool, not a crutch.

Document components effectively with Storybook 7. Setup: 1. CSF3 format for stories. 2. Autodocs for prop table generation. 3. Controls addon for prop manipulation. 4. Actions addon for event logging. 5. Interactions testing with @storybook/test. 6. Accessibility checks with a11y addon. 7. Design tokens documentation. 8. MDX for custom documentation pages. Use composition for multiple projects and implement visual testing with Chromatic.

Replace a traditional research paper with a podcast project. Subject: US History. Task: Students work in groups of 3-4 to create a 15-minute podcast episode on a historical event. Process: 1. Research Phase: Students gather information from primary and secondary sources. 2. Scripting Phase: Students write a collaborative script, including narration, sound effects, and potential interview segments. 3. Recording & Editing Phase: Students use tools like Audacity or Soundtrap to record and edit their podcast. 4. Publishing: Episodes are uploaded to a class website or platform like SoundCloud. Assessment Rubric: historical accuracy, narrative structure, audio quality, collaboration, and source citation. Allows for creativity and develops 21st-century communication skills.

Manage innovation pipeline from idea generation to product launch. Innovation stages: 1. Idea generation: customer feedback, competitor analysis, technology trends. 2. Concept validation: user interviews, prototype testing, market research. 3. Business case development: market size, revenue model, ROI analysis. 4. MVP development: minimum viable product with core features. 5. Market testing: limited release, feedback collection, iteration. 6. Scale-up: full product launch and growth optimization. Stage gates: defined criteria for advancing ideas between stages. Example criteria: Problem validation (100+ customer interviews), Market size ($100M+ TAM), Technical feasibility (prototype built). Resource allocation: 70% sustaining innovation (core product), 20% adjacent opportunities, 10% disruptive bets. Metrics: ideas in pipeline, conversion rates between stages, time-to-market. Portfolio management: balance short-term revenue with long-term growth bets. Innovation culture: hackathons, innovation time, fail-fast mentality.

Implement a 15-minute daily morning meeting in an elementary classroom. Structure (based on Responsive Classroom): 1. Greeting (3 mins): Students greet each other by name (e.g., handshake, wave, fun greeting). Builds community. 2. Sharing (4 mins): 2-3 students share something about their life. Others practice active listening and asking thoughtful questions. 3. Group Activity (5 mins): A quick, fun activity to build teamwork and communication (e.g., 'Count to 20 as a class', a short song). 4. Morning Message (3 mins): Teacher reads a daily message that sets a positive tone and outlines the day's learning. Establishes a safe, predictable start to the day and builds social skills.

Implement component testing with Cypress. Workflow: 1. Mount React/Vue components in isolation. 2. cy.get() for element selection. 3. Intercept API calls with cy.intercept(). 4. Test user interactions (click, type, drag). 5. Visual viewport testing. 6. Custom commands for reusability. 7. Fixtures for test data. 8. Time travel debugging. Use with TypeScript and implement accessibility testing with cypress-axe plugin.

Shift from traditional to student-led conferences. Preparation: 1. Students compile a portfolio of their work (successes and challenges). 2. Students complete a self-reflection sheet on their progress, goals, and areas for improvement. 3. Students practice presenting their portfolio to peers. The Conference (20 mins): 1. Student welcomes parents and teacher. 2. Student presents their portfolio, explaining their work and learning process. 3. Student discusses their self-reflection and goals for the next quarter. 4. Parents and teacher ask questions and provide feedback. 5. All parties co-sign the goal-setting sheet. Benefits: increases student ownership and accountability, develops communication skills, provides parents with a more authentic view of their child's learning.

Explore lived experiences through phenomenological inquiry. Interview design: 1. Grand tour question: 'Tell me about your experience with [phenomenon].' 2. Follow-up probes: 'What was that like?' 'Can you give me an example?' 'What did you feel?' 3. Structural questions: 'What stands out for you?' 'What was most significant?' Interview process: 1. Bracketing: researcher acknowledges preconceptions, sets them aside. 2. Phenomenological reduction: focus on essence of experience, not explanations. 3. Imaginative variation: explore different perspectives on same experience. Analysis following Colaizzi or Giorgi method: 1. Read transcripts for overall feeling. 2. Extract significant statements. 3. Formulate meaning from statements. 4. Organize into theme clusters. 5. Write exhaustive description. 6. Return to participants for validation. Sample size: typically 6-12 participants until saturation.

Organize a formal debate on the topic: 'Should the Electoral College be abolished?' Structure: Lincoln-Douglas or team-based format. Teams: Affirmative (pro-abolition) and Negative (con-abolition). Roles: speakers, researchers, rebuttal planners. Timeline: 1. Research (1 week): Teams gather evidence and prepare arguments. 2. Constructive Speeches (8 mins each team): Present initial arguments. 3. Cross-Examination (3 mins after each speech): Opposing team asks clarifying questions. 4. Rebuttal Speeches (5 mins each team): Address and refute opponents' arguments. 5. Closing Statements (3 mins each team): Summarize key points. Assessment: rubric based on strength of argument, use of evidence, rebuttal effectiveness, and public speaking skills. Teacher acts as moderator.

Create a lightweight desktop app with Tauri. Benefits: 1. Rust backend for performance and security. 2. Native webview (no bundled Chromium). 3. React/Vue/Svelte frontend. 4. Commands for Rust-to-JS communication. 5. File system API with permissions. 6. System tray and notifications. 7. Smaller bundle size vs Electron. 8. Window customization and multi-window support. Use @tauri-apps/api and implement plugin system for extensibility.

Create a role-playing simulation of the Cuban Missile Crisis. Roles: President Kennedy, Robert Kennedy, military advisors (Joint Chiefs), Soviet Ambassador, etc. Scenario: Students receive role-specific briefing documents with classified information and objectives. Process: 1. Students meet in their advisory groups to discuss options. 2. The 'President' facilitates a series of meetings where advisors present their cases (e.g., blockade vs. air strike). 3. The 'President' makes a decision. 4. Teacher reveals the historical outcome. Debrief: Students reflect on the pressures of decision-making, the role of information, and the consequences of different choices. Compare their simulation outcome to the actual historical events.

Build compelling creative portfolio that showcases skills and attracts ideal opportunities. Portfolio structure: 1. Hero projects: 3-5 best pieces that demonstrate range and expertise. 2. Case studies: process documentation, problem-solution narrative, results achieved. 3. Skill diversity: show versatility across mediums while maintaining focused specialty. 4. Personal projects: demonstrate passion and creative initiative beyond client work. Project presentation format: 1. Challenge/objective statement (2-3 sentences). 2. Solution approach and creative process. 3. Visual execution with context and rationale. 4. Results and impact measurement where applicable. 5. Credits for collaborative work. Platform considerations: 1. Personal website: custom domain, fast loading, mobile optimized. 2. Behance/Dribbble: industry-standard platforms for creative discovery. 3. LinkedIn: professional context with work samples. Content curation: quality over quantity, update quarterly, remove outdated work. Personal branding: consistent visual identity, unique value proposition, authentic voice and perspective. SEO optimization: relevant keywords, project descriptions, alt text for images.

Implement a digital portfolio as a final assessment in a visual arts course. Platform: Google Sites, Behance, or Adobe Portfolio. Portfolio Contents: 1. Best Works: 5-7 of the student's strongest pieces from the semester. 2. Process Work: Include sketches, drafts, and experiments for at least two pieces to show development. 3. Artist's Statement: A written reflection on their artistic style, influences, and growth over the semester. 4. Critiques: Include a written self-critique of one piece and a reflection on feedback received from peers or the teacher. Assessment: Rubric evaluates artistic skill, creative expression, growth over time (evidenced by process work), and reflective analysis. The portfolio provides a more holistic view of student learning than a single final project.

Develop with Expo's managed workflow. Features: 1. Over-the-air updates with EAS Update. 2. No native code compilation needed. 3. Expo SDK for native functionality. 4. Development builds for custom native code. 5. Easy third-party library integration. 6. QR code app distribution. 7. Push notifications setup. 8. App icon and splash screen generation. Build with EAS Build and submit to stores. Use expo-router for file-based routing.

Write a grant proposal to fund a 1:1 Chromebook initiative. Proposal Sections: 1. Needs Statement: Use data to demonstrate the need (e.g., current device-to-student ratio, state testing requirements, digital divide statistics). 2. Project Description: Detail the plan to provide a Chromebook for every student, including implementation timeline, professional development for teachers, and digital citizenship curriculum. 3. Goals and Objectives: State clear, measurable goals (e.g., 'By Year 2, 100% of students will have access to a device, and teachers will integrate technology in 75% of lessons'). 4. Budget: Provide a detailed line-item budget for devices, cases, management software, and teacher training stipends. 5. Evaluation Plan: Explain how you will measure the project's success (e.g., usage data, teacher surveys, student achievement data). Research potential funders (local foundations, tech company grants).

Maximize internal validity through experimental control. Threats to internal validity (Campbell & Stanley): 1. History: external events during study. Control: randomization, brief study duration. 2. Maturation: natural changes over time. Control: control group, random assignment. 3. Testing: effects of pretesting. Control: Solomon four-group design, posttest-only design. 4. Instrumentation: changes in measurement. Control: standardized protocols, calibration. 5. Regression to mean: extreme scores regress toward average. Control: random assignment, cutoff-based assignment analysis. 6. Selection: systematic differences between groups. Control: randomization, matching. 7. Mortality: differential dropout. Control: intent-to-treat analysis, retention strategies. Design features: random assignment is gold standard. Manipulation checks ensure independent variable was successfully manipulated. Attention controls eliminate placebo effects.

Teach students to analyze primary sources like a historian. Framework: Sourcing, Contextualizing, Close Reading, Corroborating (Stanford History Education Group - SHEG). Activity: Give students two primary source documents about the Boston Massacre—one from a British officer, one from a colonial patriot. Analysis Steps: 1. Sourcing: Who wrote this? When? Why? Is it reliable? 2. Contextualizing: What was happening at the time that might influence this account? 3. Close Reading: What claims does the author make? What words do they use to persuade the reader? 4. Corroborating: How do the two accounts differ? Where do they agree? Which account is more believable and why? This moves students from memorizing facts to interpreting evidence.

Implement navigation in React Native apps. Patterns: 1. Stack navigator for hierarchical screens. 2. Tab navigator for main sections. 3. Drawer navigator for side menu. 4. Deep linking and universal links. 5. Screen transitions and gestures. 6. Nested navigators composition. 7. Authentication flow routing. 8. Persistent navigation state. Use React Navigation v6 with TypeScript for type-safe routes and implement header customization.

Design an engaging 90-minute PD session on a new instructional strategy. Agenda: 1. Why (10 mins): Start with research or data showing the need for the strategy. 2. What (20 mins): Clearly explain and model the strategy. Show a video of it in action. 3. How (30 mins): Active engagement. Have teachers try the strategy themselves (e.g., plan a short lesson segment using it). 4. What If (15 mins): Facilitate a discussion about potential challenges and solutions for implementation in their own classrooms. 5. Now What (15 mins): Teachers set a specific goal for how they will try the strategy in the next week. Provide a resource handout. Avoid 'sit and get'; prioritize active learning and collaboration.

Master ghostwriting by capturing authentic client voice while maintaining professional standards. Voice analysis process: 1. Sample collection: existing writing, speeches, interviews, social media posts. 2. Pattern identification: sentence structure, vocabulary preferences, humor style. 3. Interview sessions: ask about influences, communication style, key messages. 4. Voice profile creation: tone characteristics, topics of expertise, personal anecdotes. Voice matching techniques: 1. Syntax mimicry: sentence length patterns, complexity levels. 2. Vocabulary alignment: technical vs. casual language, industry jargon. 3. Perspective consistency: optimistic vs. cautious outlook, formal vs. conversational. 4. Signature phrases: recurring expressions, unique metaphors. Content development: 1. Outline approval: structure and key points before writing. 2. Draft iterations: initial version, client feedback, refinements. 3. Fact verification: accuracy of claims, proper attribution. 4. Final review: client approval before publication. Professional boundaries: 1. Credit agreements: byline attribution, recognition terms. 2. Confidentiality: non-disclosure of proprietary information. 3. Intellectual property: ownership rights, future use permissions. Project types: books, articles, speeches, blog posts, social media content, thought leadership pieces.

Teach students to use graphic organizers to deconstruct text. Types of Organizers: 1. Story Map: For fiction. Fields for characters, setting, problem, key events, and resolution. 2. Venn Diagram: For comparing and contrasting two concepts, characters, or texts. 3. KWL Chart: Before reading non-fiction. Columns for 'What I Know', 'What I Want to Know', and 'What I Learned'. 4. Cause and Effect Chain: For history or science texts. Shows the sequence of events leading to an outcome. 5. Frayer Model: For vocabulary. A four-square chart with definition, characteristics, examples, and non-examples. Model how to use each organizer with a shared text before asking students to use them independently.

Implement GraphQL with Apollo Client. Setup: 1. ApolloProvider with InMemoryCache. 2. useQuery hook for data fetching. 3. useMutation for data updates. 4. Optimistic UI responses. 5. Cache policies (cache-first, network-only). 6. Fragment composition for reusable fields. 7. Pagination with fetchMore. 8. Local state management. Use codegen for TypeScript types and implement error handling with Error Link.

Conduct an outdoor lesson in a schoolyard or local park. Topic: Ecosystems. Activity: 'Bio-Blitz'. 1. Preparation: Define a 10x10 meter area. Provide students with field guides, magnifying glasses, and data collection sheets. 2. The Blitz (30 mins): In small groups, students identify and count as many different species of plants and animals as they can find in their designated area. They can use apps like iNaturalist for identification. 3. Data Analysis (15 mins): Back in the classroom, groups pool their data to calculate the biodiversity of the area. Create a food web diagram based on the organisms they found. 4. Reflection (10 mins): Discuss human impact on the local ecosystem. Fosters observation skills, appreciation for nature, and understanding of ecological concepts.

Develop next generation of researchers through effective mentoring. Mentoring models: 1. Dyadic: traditional one-on-one mentor-mentee relationship. 2. Team mentoring: multiple mentors with different expertise areas. 3. Peer mentoring: lateral relationships between researchers at similar career stages. 4. Group mentoring: mentor works with cohort of mentees simultaneously. Mentoring competencies: 1. Research skills: methodology, analysis, writing, grant writing. 2. Professional development: networking, career planning, work-life balance. 3. Personal support: confidence building, resilience, identity development. Structure and process: 1. Goal setting: specific, measurable objectives for mentoring relationship. 2. Regular meetings: monthly face-to-face or virtual meetings with agenda. 3. Progress monitoring: quarterly reviews of goal achievement and relationship satisfaction. 4. Feedback: bidirectional feedback on mentoring effectiveness. Training programs: 1. Mentor training: active listening, giving feedback, cultural competence. 2. Mentee training: goal setting, communication, relationship management. Evaluation: surveys, focus groups, career outcome tracking for evidence-based improvement.

Transition from traditional points-based grading to standards-based grading (SBG). Principles: 1. Grades reflect mastery of standards, not behavior or effort. 2. Separate academic grades from 'habits of work' grades (e.g., participation, timeliness). 3. Use a 4-point scale (e.g., 4=Exceeds, 3=Meets, 2=Approaching, 1=Beginning) for each standard. 4. Allow for reassessment: students can retake assessments to demonstrate improved mastery. Report Card: Instead of a single subject grade (e.g., 'B+ in Math'), the report card lists key standards with a proficiency level for each (e.g., 'Solves multi-step equations: 3', 'Calculates area and perimeter: 2'). Communication: Requires clear communication with parents and students about the philosophy and mechanics of the new system.

Build type-safe APIs with tRPC. Architecture: 1. Define routers with input/output schemas. 2. Zod for runtime validation. 3. Automatic TypeScript inference. 4. React Query integration for client. 5. Middleware for auth and logging. 6. Context for user sessions. 7. Subscriptions with WebSockets. 8. Error handling with TRPCError. No code generation needed. Use with Next.js or standalone Express server.

Create a digital escape room for a unit review using Google Forms. Theme: 'Escape the Mad Scientist's Lab' for a science unit. Structure: 1. Create a Google Form with multiple sections. 2. Set up 'response validation' for each question, so students can only proceed to the next section if they answer correctly. This acts as the 'lock'. 3. The questions are puzzles related to the unit content (e.g., a riddle about mitosis, a coded message with vocabulary words). 4. The final section reveals a 'You Escaped!' message. 5. Use a storyline to connect the puzzles. Share the form with students to complete in small groups. Promotes collaboration, problem-solving, and engagement.

Master poetic techniques for powerful creative expression and emotional resonance. Poetic devices: 1. Metaphor: direct comparison without 'like' or 'as' (life is a journey). 2. Simile: comparison using 'like' or 'as' (brave as a lion). 3. Personification: human qualities to non-human objects. 4. Alliteration: repeated initial consonant sounds. 5. Assonance: repeated vowel sounds within lines. Form structures: 1. Free verse: no prescribed rhyme or meter, natural speech patterns. 2. Sonnet: 14 lines, specific rhyme schemes (Shakespearean, Petrarchan). 3. Haiku: 5-7-5 syllable structure, nature imagery, moment capture. 4. Villanelle: 19 lines, two refrains, specific rhyme pattern. Imagery techniques: 1. Sensory details: sight, sound, smell, taste, touch descriptions. 2. Concrete specifics: particular objects rather than abstractions. 3. Juxtaposition: contrasting images for emotional impact. Line and stanza craft: 1. Enjambment: lines flowing into next without grammatical pause. 2. Caesura: deliberate pause within line for emphasis. 3. White space: strategic use of silence, breath, reflection. Revision process: multiple drafts focusing on word choice, rhythm, emotional truth, unnecessary word elimination.

Organize a classroom library to maximize student use. Organization: 1. Leveling: Use a system like Fountas & Pinnell or Lexile levels, but keep it simple for students (e.g., color-coded stickers). 2. Bins & Baskets: Sort books into bins labeled by genre (fantasy, mystery, biography), author (e.g., a Roald Dahl bin), topic (animals, sports), and series (Harry Potter). 3. Display: Feature new or high-interest books face-out on shelves. Create a 'teacher recommendations' section. 4. Check-out System: Use a simple system like a sign-out binder or a digital tool (e.g., Booksource Classroom). 5. Student Involvement: Assign 'librarian' as a classroom job to help manage the library. Regularly survey students on what books they want to see added.

Manage state simply with Zustand. Implementation: 1. create() store with actions. 2. Minimal boilerplate vs Redux. 3. No providers needed. 4. Middleware for persistence. 5. Devtools integration. 6. Slices pattern for large stores. 7. Immer for mutations. 8. TypeScript support. Use selectors to prevent unnecessary renders and implement computed values with get() in store.

Set up and manage a class blog to provide an authentic audience for student writing. Platform: Edublogs, Kidblog, or a private Blogger site. Process: 1. Setup: Create the blog, establish categories (e.g., book reviews, science reports, creative writing), and teach students how to use the platform. 2. Digital Citizenship: Teach lessons on appropriate online commenting and respecting intellectual property. 3. Writing & Publishing: Students draft posts, receive peer and teacher feedback, revise, and then publish their work on the blog. 4. Audience: Share the blog link with parents and other classes. Encourage comments from readers. 5. Student Roles: Assign student editors, moderators, and social media managers (for a closed class account). Turns writing assignments into meaningful communication.

Conduct quantitative meta-analysis following best practices. Data preparation: 1. Extract effect sizes and standard errors from each study. 2. Code study characteristics (sample size, population, methodology quality). 3. Handle multiple effect sizes from same study (average, select one, or use robust variance estimation). Statistical analysis in R metafor package: 1. Fixed effects model: assumes one true effect size. 2. Random effects model: assumes distribution of true effects. 3. Test for heterogeneity using Q-statistic and I² (>75% = high heterogeneity). 4. Moderator analysis: meta-regression or subgroup analysis to explain heterogeneity. 5. Publication bias assessment: funnel plots, Egger's test, trim-and-fill method. Report: Forest plot showing individual study effects and pooled estimate with 95% CI. Address limitations and clinical significance of findings.

Design a systematic literature review following PRISMA guidelines. Protocol steps: 1. Define research question using PICO framework (Population, Intervention, Comparison, Outcome). 2. Develop search strategy: identify 3-5 databases (PubMed, Scopus, Web of Science), create Boolean search terms, set inclusion/exclusion criteria. 3. Screen titles/abstracts independently by 2 reviewers, resolve conflicts with third reviewer. 4. Full-text review using predefined criteria. 5. Data extraction using standardized forms (study design, sample size, outcomes, bias assessment). 6. Quality assessment using appropriate tools (Cochrane Risk of Bias, Newcastle-Ottawa Scale). 7. Synthesize findings narratively or through meta-analysis if appropriate. Document decisions transparently. Register protocol in PROSPERO before starting.

Implement SWR for optimal data experience. Pattern: 1. useSWR hook with cache key. 2. Return stale data immediately. 3. Revalidate in background. 4. Dedupe simultaneous requests. 5. Focus revalidation. 6. Interval polling for real-time feel. 7. Error retry with exponential backoff. 8. Mutation with useSWRMutation. Use globally for all requests and implement dependent fetching for serial queries.

Create business model with canvas. Components: 1. Value Propositions (what you offer). 2. Customer Segments (who you serve). 3. Channels (how customers find you). 4. Customer Relationships (engagement type). 5. Revenue Streams (how you make money). 6. Key Resources (assets needed). 7. Key Activities (what you do). 8. Key Partnerships (who helps). 9. Cost Structure (expenses). Use for lean validation and iteration.

Write compelling grant proposals with high funding success rates. Proposal structure: 1. Specific Aims (1 page): state problem clearly, propose solution, highlight innovation and significance. 2. Research Strategy: Significance (why important), Innovation (what's new), Approach (how to do it). 3. Budget justification: personnel (effort percentages), equipment, supplies, indirect costs. Pre-writing: 1. Read funding agency priorities and review criteria. 2. Study successful proposals in your field. 3. Contact program officer for informal feedback on concept. Writing strategy: 1. Lead with impact: what difference will this make? 2. Use visual elements: figures, flowcharts, timelines. 3. Address reviewer concerns preemptively. 4. Get external reviews before submission. Common mistakes: aims too ambitious, insufficient preliminary data, weak methodology, unclear significance. Timeline: start 3-6 months before deadline, allow time for institutional review.

Implement OKRs effectively. Structure: 1. Objective (what you want to achieve - qualitative). 2. Key Results (how you measure - quantitative, 3-5 per objective). 3. Quarterly cadence. 4. Company, team, and individual OKRs. 5. Ambitious yet achievable (70% completion is good). 6. Regular check-ins. 7. Public visibility. 8. Separate from performance reviews. Focus on outcomes not outputs. Align across organization.

Conduct SWOT analysis. Framework: 1. Strengths (internal positives). 2. Weaknesses (internal negatives). 3. Opportunities (external positives). 4. Threats (external negatives). Process: Brainstorm each quadrant, prioritize items, develop strategies (SO: leverage strengths for opportunities, WO: address weaknesses to capture opportunities, ST: use strengths to mitigate threats, WT: defensive plan). Use for strategic decisions and positioning.

Master visual composition using mathematical principles and design rules. Golden Ratio (1:1.618): 1. Golden rectangle: most pleasing proportional relationship. 2. Golden spiral: natural flow for eye movement through design. 3. Application: crop photos, position focal points, create balanced layouts. Rule of Thirds: divide canvas into 9 equal sections, place key elements at intersection points. Leading lines: use diagonal, curved, or straight lines to direct viewer attention to focal point. Visual hierarchy: 1. Size: larger elements attract attention first. 2. Color: bright, contrasting colors draw focus. 3. Position: top-left to bottom-right scanning pattern (Western cultures). 4. Whitespace: negative space creates breathing room, emphasizes content. Balance types: 1. Symmetrical: formal, stable feeling. 2. Asymmetrical: dynamic, modern appearance. Tools: Adobe Creative Suite grid systems, Figma layout grids, photography composition apps for rule of thirds overlay.

Create compelling pitch deck. Slide structure: 1. Problem (pain point). 2. Solution (your product). 3. Market Opportunity (TAM/SAM/SOM). 4. Product Demo. 5. Business Model. 6. Traction (metrics, growth). 7. Competition (differentiation). 8. Team (why you). 9. Financials. 10. Ask (amount raising, use of funds). Keep to 10-15 slides. Tell a story. Practice delivery. Visual over text.

Build financial projections. Components: 1. Revenue forecast (customers × price × conversion). 2. Cost of Goods Sold. 3. Operating expenses (fixed + variable). 4. EBITDA and net income. 5. Cash flow statement. 6. Balance sheet projections. 7. Break-even analysis. 8. Scenario modeling (best/worst/realistic). Use conservative assumptions. Update monthly. Essential for fundraising.