--- title: "Copy a CLAUDE.md template for your role and adapt it in 30 minutes" description: "Five CLAUDE.md templates for business owners, consultants, content creators, developers, and educators, with routing tables and steps to adapt each one." canonical: "https://scalewithsearch.com/articles/claude-md-template-examples" date: "2026-01-28" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Copy a CLAUDE.md template for your role and adapt it in 30 minutes. You know that a `CLAUDE.md` file gives Claude Code standing context. You open a blank Markdown file and do not know what to put in it. Many people stop at that point. This article gives you five complete templates: business owner, consultant, content creator, developer, and educator. Pick the one closest to your work, copy it, and fill in your details. The customization takes about 30 minutes. ## Know what each template contains A `CLAUDE.md` helps only when its structure is right. Too vague, and Claude Code has nothing to apply. Too detailed, and the useful rules drown in text. Each template below holds five parts: | Part | What it tells Claude Code | |---|---| | WHO | Your role, schedule, and situation | | WHAT | The domains of your work that need different instructions | | Routing table | The keywords that load each domain's context file | | VOICE | How Claude Code should write for you | | RULES | What Claude Code must never do | Replace every bracketed section with your details and save the file as `CLAUDE.md` at the root of your vault or project folder. A template is context, not a lock. A rule such as "customer data is sacred" tells Claude Code what to try. It does not stop a read or a send. Put hard limits in permission settings, and read the [business CLAUDE.md template](/articles/claude-md-template-business-context) for sources, exclusions, and stopping rules. ## Template 1: business owner You run a business with several departments and switch context all day. Claude Code must know whether you are talking about customers, the team, or strategy. ``` # [Your Name]'s Business ## WHO [Your name], [Company name]: [what you sell] **Team:** [number] employees **Revenue:** [stage/size] **Customers:** [who you serve] **My role:** [CEO/Founder/Owner]: [main responsibilities] ## WHAT (Domains) | Domain | Context File | Load when prompt mentions... | |--------|--------------|------------------------------| | **Sales** | `Sales/_context.md` | lead, pipeline, customer, deal, proposal, pricing | | **Operations** | `Operations/_context.md` | process, team, workflow, systems, efficiency | | **Marketing** | `Marketing/_context.md` | campaign, content, ad, email, social, traffic | | **Finance** | `Finance/_context.md` | revenue, expense, budget, forecast, cash flow | ## VOICE Direct. No corporate speak. Write like you talk. Use "we" when talking about the company. Use "I" for personal decisions. If it sounds like it came from a marketing agency, rewrite it. ## RULES 1. Read before edit: never modify a file without reading it first 2. Ask if unclear: don't guess, ask 3. Date format: YYYY-MM-DD always 4. Keep responses dense: no fluff, no disclaimers 5. Customer data is sacred: never share outside prompts, never assume permission ## KEY FILES - `Sales/Active-Deals.md`: current pipeline - `Operations/Team.md`: who does what - `Marketing/Campaign-Calendar.md`: what's live, what's next - `Finance/Metrics-Dashboard.md`: key numbers ## CURRENT STATE **Q[X] [YEAR] priorities:** 1. [Priority 1] 2. [Priority 2] 3. [Priority 3] **Active projects:** - [Project A]: [status] - [Project B]: [status] **Team updates:** - [Recent change or important context] ``` To adapt it, replace the bracketed sections, add your real domain folders, and list your real priorities. Update CURRENT STATE each month. ## Template 2: consultant You have several clients, each with different needs, people, and communication styles. Claude Code must switch client context when you name the client. ``` # [Your Name]: [Consulting Focus] ## WHO [Your name], independent consultant **Specialty:** [what you help with] **Clients:** [number] active, [number] total **Rates:** [rate] per hour or [project basis] **Schedule:** [typical availability] ## WHAT (Clients) | Client | Context File | Load when prompt mentions... | |--------|--------------|------------------------------| | **[Client A]** | `Clients/[ClientA]/_context.md` | [ClientA], [key contact name], [project names] | | **[Client B]** | `Clients/[ClientB]/_context.md` | [ClientB], [key contact name], [project names] | | **[Client C]** | `Clients/[ClientC]/_context.md` | [ClientC], [key contact name], [project names] | ## CLIENT STRUCTURE Each client folder contains: - `_context.md`: client overview, contacts, current projects - `Deliverables/`: work product - `Meetings/`: notes and decisions - `Communication/`: email drafts, status updates ## VOICE Professional but not stiff. Clients hired me for expertise, not corporate polish. Write tight. Clients pay by the hour. Respect their time. ## RULES 1. Client files stay separate: never mix client data 2. Read client context before writing anything: voice and needs differ 3. Track billable work: note time spent on deliverables 4. Ask before sharing anything: client work is confidential 5. Use client-specific templates when they exist ## DELIVERABLES Standard deliverables: - **Strategy docs:** [template location] - **Client reports:** [template location] - **Recommendations:** [template location] - **Meeting recaps:** [template location] ## CURRENT STATE **Active projects:** - [Client A]: [project], due [due date], [status] - [Client B]: [project], due [due date], [status] - [Client C]: [project], due [due date], [status] **Upcoming:** - [What's next this week/month] **Pipeline:** - [Prospects or proposals out] ``` To adapt it, add one row and one folder for each client. Update CURRENT STATE after each client meeting. The rule "client files stay separate" needs a test as well as a sentence. The [client context separation article](/articles/separate-client-context-before-agent-work) shows how to run one. ## Template 3: content creator You publish on several platforms, in several formats, for different audiences. Claude Code must match your voice and know what you already covered. ``` # [Your Name]: [Your Content Niche] ## WHO [Your name], [creator type] focusing on [topic] **Platforms:** [YouTube/Newsletter/Blog/Podcast/Social] **Audience:** [who watches/reads/listens] **Publishing schedule:** [frequency] **Voice:** [how you describe your style] ## WHAT (Content Types) | Type | Context File | Load when prompt mentions... | |--------|--------------|------------------------------| | **Articles** | `Content/Articles/_context.md` | article, blog, post, SEO, write | | **Video** | `Content/Video/_context.md` | video, script, YouTube, thumbnail | | **Newsletter** | `Content/Newsletter/_context.md` | newsletter, email, subscribers | | **Social** | `Content/Social/_context.md` | tweet, post, LinkedIn, Instagram | ## VOICE RULES **Write like I talk:** - [Voice characteristic 1] - [Voice characteristic 2] - [Voice characteristic 3] **Never use:** - [Banned words/phrases you hate] - [Corporate speak or buzzwords] - [Overused creator clichés] **Sentence rhythm:** - [Short/long preference] - [Contractions yes/no] - [Technical level] ## CONTENT RULES 1. Check past content before suggesting topics: don't repeat myself 2. Match platform voice: newsletter sounds different than Twitter 3. Use my examples and stories: they're in `Stories.md` 4. Follow platform specs: character limits, formatting, best practices 5. Include CTAs where appropriate: templates in `CTAs.md` ## TOPICS I COVER **Core topics:** - [Topic area 1] - [Topic area 2] - [Topic area 3] **Avoid:** - [Topics you don't cover] - [Political/controversial areas] ## CURRENT STATE **This month's content:** - [What's published] - [What's in progress] - [What's planned] **Performance notes:** - [What's working] - [What's not] **Ideas queue:** - [Topics you're considering] ``` To adapt it, fill in your real platforms, list the words you never want in your content, and add the topics you cover. Keep the ideas queue current. For a writer with client work, the [Claude Code setup for content writers](/articles/claude-code-for-content-writers) extends this template with client folders and topic logs. ## Template 4: developer You build software across several projects, stacks, and clients or employers. Claude Code must know the active project and your code style. ``` # [Your Name]: [Developer Type] ## WHO [Your name], [full-stack/frontend/backend/mobile] developer **Focus:** [primary languages/frameworks] **Currently:** [employed/freelance/building own projects] **Location:** [timezone for scheduling] ## WHAT (Projects) | Project | Context File | Load when prompt mentions... | |--------|--------------|------------------------------| | **[Project A]** | `Projects/[ProjectA]/_context.md` | [project name], [tech stack], [client name] | | **[Project B]** | `Projects/[ProjectB]/_context.md` | [project name], [tech stack], [client name] | | **Personal** | `Personal/_context.md` | side project, experiment, learning | ## CODE STYLE **Languages I use:** - [Language 1]: [preferred style guide or conventions] - [Language 2]: [preferred style guide or conventions] **Principles:** - [Code philosophy 1] - [Code philosophy 2] - [Code philosophy 3] **Never:** - [Anti-patterns you avoid] - [Libraries/frameworks you don't use] ## RULES 1. Read project context before suggesting code: tech stack matters 2. Include error handling: don't show me happy-path-only code 3. Comment complex logic: future me needs to understand this 4. Follow project conventions: consistency beats personal preference 5. Test before claiming it works: if you can't test it, say so ## TECH STACK **Primary:** - [Stack you use most] **Secondary:** - [Stack you know but use less] **Learning:** - [Tech you're currently learning] ## PROJECT STRUCTURE Each project folder contains: - `_context.md`: tech stack, architecture, current tasks - `README.md`: project overview and setup - `Tasks.md`: what's next - `Decisions.md`: why we built it this way ## CURRENT STATE **Active work:** - [Project A]: [current task]; blockers: [blockers if any] - [Project B]: [current task]; blockers: [blockers if any] **Recently solved:** - [Problem you recently solved] **Stuck on:** - [What you're debugging or researching] ``` To adapt it, list your real projects, stack, and code conventions. Update CURRENT STATE at the start of each work session. Keep volatile facts such as client status in the project `_context.md`, not in the root file. The [context file versus CLAUDE.md guide](/articles/context-file-vs-claude-md-business-project) explains the split. ## Template 5: educator You teach several courses at different levels in varied formats. Claude Code must know what you taught and how you explain things. ``` # [Your Name]: [Teaching Focus] ## WHO [Your name], [educator/instructor/teacher] specializing in [subject] **Teaching:** [where you teach] **Students:** [who you teach] **Courses:** [number] active **Format:** [in-person/online/hybrid] ## WHAT (Courses) | Course | Context File | Load when prompt mentions... | |--------|--------------|------------------------------| | **[Course A]** | `Courses/[CourseA]/_context.md` | [course name], [topic], [student level] | | **[Course B]** | `Courses/[CourseB]/_context.md` | [course name], [topic], [student level] | | **[Course C]** | `Courses/[CourseC]/_context.md` | [course name], [topic], [student level] | ## TEACHING PHILOSOPHY **How I explain things:** - [Teaching principle 1] - [Teaching principle 2] - [Teaching principle 3] **What I avoid:** - [Teaching anti-pattern 1] - [Teaching anti-pattern 2] ## RULES 1. Match student level: don't over-simplify for advanced students or overwhelm beginners 2. Use examples from course materials: students need consistency 3. Build on previous lessons: check what's been covered 4. Include practice opportunities: reading isn't learning 5. Cite sources when using external materials ## COURSE STRUCTURE Each course folder contains: - `_context.md`: course overview, student level, current topic - `Syllabus.md`: course outline and schedule - `Lessons/`: individual lesson plans - `Assessments/`: quizzes, tests, projects - `Resources/`: readings, examples, references ## CONTENT TYPES **I create:** - Lesson plans: [template location] - Lecture slides: [format preferences] - Assessments: [types you use] - Handouts: [style and format] - Discussion prompts: [how you structure them] ## CURRENT STATE **This week's teaching:** - [Course A]: [topic], lesson [lesson number] - [Course B]: [topic], lesson [lesson number] **What's working:** - [Successful lesson or approach] **What needs work:** - [Concept students struggle with] **Upcoming:** - [Major assignments or exams] - [New material to prepare] ``` To adapt it, add your real courses and describe how you teach in the philosophy section. Update CURRENT STATE each week, so Claude Code knows where the students are. ## Put the template to work 1. Copy the template closest to your work. 2. Replace every bracketed section with your real information. 3. Save the file as `CLAUDE.md` at the root of your vault or project folder. 4. Create the domain folders that the routing table names. 5. Add a `_context.md` in each domain folder with the details for that area. 6. Test the setup. Ask Claude Code for a task in one domain, and check that it loaded the right context. The first version will not be perfect. Refine it from real sessions. The [Claude Code setup guide](/articles/claude-code-setup-guide) shows how to confirm which memory files loaded. ## Test the routing table for keyword collisions A routing table fails quietly when one word appears in two rows. Claude Code then loads the wrong context file, or both files, and the draft mixes two voices. The templates above have this fault in places, so check your copy before you rely on it. The content creator template shows the problem. The word "post" appears in the Articles row and in the Social row. The word "write" sits in the Articles row, and almost every request contains it. A request such as "Write a LinkedIn post about the new video" matches Articles, Video, and Social at once. The business owner template has a smaller version: "email" loads Marketing, but an email to a customer about a price is sales work. Run this check on your own table: 1. List every trigger word from every row. 2. Mark each word that appears in two rows. 3. Mark each word that most requests contain, such as "write" or "draft". 4. Write five requests that you make each week, and predict the row each one should load. 5. Run each request in a new session, and ask Claude Code which context file it read. 6. Fix each miss with a narrower word or a tie-break rule. For the content creator template, remove "write" and "post" from the Articles row, and keep "post" only in the Social row. Then add a tie-break rule to CONTENT RULES. When a request matches two rows, Claude Code loads the row for the output format. It reads the other row only when the request names it as a source. The routing table is an instruction that Claude Code reads, not code that runs. Claude Code usually follows it, but it can misjudge an unclear request. When a wrong load can expose client data, move the routing into a `UserPromptSubmit` hook, which runs the same way on every prompt. ## Date the CURRENT STATE section Every template ends with CURRENT STATE, and that section goes stale first. A file that still lists last month's priorities gives confident answers about finished work. Suppose the consultant template shows a Client A report due on the 5th, and the report went out a week ago. Claude Code then drafts a reminder for work that is already done. Add a date line under the heading, such as `Last updated: 2026-09-25`. Then add one rule: if CURRENT STATE is more than 14 days old, say so before you use it. Update the section on the schedule that each template names. That is monthly for the business owner, after each client meeting for the consultant, and weekly for the educator. ## Mix sections when one template does not fit Few people fit one category. You may be a consultant who publishes content, a developer with a side business, or an educator who sells a course. Mix the sections. Take the client routing from the consultant template. Add the voice rules from the content creator template. Use the tech stack section from the developer template. The file should reflect how you work, not a category. ## Worked example: one request through the file With the file in place, Claude Code reads it at the start of each session. Suppose you use the consultant template and type, "Draft the client update for Client B." Claude Code checks the routing table and finds Client B's row. It loads `Clients/[ClientB]/_context.md` for the contacts and current project. It finds the client report template in the DELIVERABLES section. It applies the VOICE section: professional, tight, no corporate polish. It follows rule 1 and reads nothing from Client A's folder. The draft names the right project, the right due date, and the right contact. You did not paste anything or explain the client again. ## Related: AI memory - [Find where Claude Code /init stops and plan the memory it leaves out](/articles/claude-code-init-limitations) - [Turn repeated AI formatting instructions into rules the model reads every session](/articles/ai-doesnt-follow-my-instructions) - [Write down the business facts AI cannot guess before you ask for a draft](/articles/ai-doesnt-understand-my-business) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```