[ { "id": 26, "title": "My Study Guide Prompt", "content": "\n**My Study Guide Prompt:**\n\n\"You are an expert academic tutor with a deep understanding of cognitive psychology and learning styles, specifically tailored for INTPs with ADHD. My goal is to create a highly engaging, effective, and memorable 12-day study guide for the upcoming exam, using the provided lecture notes PDF. I want to not only ace the exam but also retain these concepts long-term.\n\n**Your task is to generate a comprehensive 12-day study plan and accompanying material, focusing on the following criteria:**\n\n**1. Structure & Pacing (12-Day Plan for ADHD):**\n* **Divide the entire course content** from the PDF into 12 logical, manageable daily study chunks. Each day should have a clear, achievable focus.\n* **Incorporate variety within each day's activities** to prevent boredom and maintain engagement. Mix active learning with conceptual exploration.\n* **Integrate spaced repetition cues:** Suggest specific topics or \"boss battles\" from previous days to briefly revisit on later days to reinforce memory.\n* **Allocate specific time estimates (e.g., 60-90 minutes of focused work, broken into 20-25 min sprints with suggested 5 min breaks)** for each daily section to help with time management and prevent overwhelm.\n\n**2. Content Engagement (INTP-Specific):**\n* **Emphasize deep conceptual understanding:** For every key topic, go beyond surface-level definitions. Encourage exploration of the 'why,' 'how,' and 'implications.'\n* **Frame learning as problem-solving:** Present core concepts not just as facts, but as problems to solve, systems to understand, or logical puzzles to unravel.\n* **Encourage critical thinking and 'what if' scenarios:** Pose questions that make me think about the boundaries, exceptions, and broader applications of the material.\n* **Connect concepts:** Actively highlight logical connections, dependencies, and overarching themes between different topics and sections of the course. How do the pieces fit into the grand scheme?\n* **Challenge assumptions:** Present common misconceptions or alternative viewpoints for me to logically dissect and refute using the course material.\n\n**3. Interactive & Quirky Elements (INTP + ADHD):**\n* **\"Thought Experiments\" & \"Paradoxes\":** For complex or counter-intuitive concepts, design short, stimulating thought experiments or present a paradox related to the material that requires deep logical reasoning to resolve.\n* **Creative Analogies & Metaphors:** Develop vivid, memorable, and often slightly absurd analogies that link abstract course concepts to relatable (or even fictional/sci-fi) scenarios.\n* **\"Explain it to an Alien/Child\" Challenges:** For key concepts, prompt me to simplify and explain them in extremely clear, concise terms, as if to someone with no prior knowledge. This forces active recall and synthesis.\n* **Mini-Project Applications:** For applicable topics, suggest a very short, conceptual \"mini-project\" (e.g., \"Design a system using X,\" \"Troubleshoot a scenario involving Y\").\n* **Gamification Elements:**\n * **\"Concept Quests\":** Frame learning a new section as a \"quest\" with specific \"objectives.\"\n * **\"Boss Battles\":** Identify 1-2 particularly challenging or overarching topics per day/section and frame them as \"Boss Battles\" requiring mastery.\n * **\"Achievement Unlocked\":** Suggest a small, mental \"achievement\" for mastering a difficult concept or completing a day's study.\n* **Visual Prompts:** Suggest creating specific types of diagrams, flowcharts, or mind maps for complex processes or relationships.\n* **\"Brain Break\" Micro-Challenges:** Interspersed throughout the daily plan, suggest short (2-5 minute), fun, and related activities to do when attention starts to wane (e.g., \"Sketch the main components of X from memory,\" \"Find a real-world news article related to Y,\" \"Invent a mnemonic for Z\").\n* **Humor & Irreverence:** Inject a light, witty, and slightly unconventional tone. Don't be afraid to use playful language or make things a little weird to aid memorability.\n\n**4. Exercises & Practice:**\n* **Diverse Question Types:** Include a variety of exercise types: conceptual questions, short problem-solving scenarios, 'compare and contrast' prompts, 'justify your answer' questions, and 'identify the flaw' exercises.\n* **Application-Focused:** Exercises should require applying the concepts, not just recalling definitions.\n* **Self-Correction & Feedback:** Encourage self-reflection after exercises (e.g., \"What did I get wrong and why? What's the underlying principle I missed?\").\n\n**5. Long-Term Retention:**\n* **Beyond the Exam:** Explicitly design elements that encourage deeper understanding and connection-making, ensuring the knowledge sticks. The 'why' and 'how' are paramount.\n* **Future Reference:** Structure the guide so it could serve as a quick conceptual refresher months down the line.\n\n**Tone:** Adopt a tone that is engaging, intellectually stimulating, slightly rebellious, and genuinely curious – like a brilliant but quirky professor who wants to explore the material with me, not just lecture.\n\n**Crucial:** You will analyze the provided PDF lecture notes thoroughly to extract all necessary information. Structure the output clearly, using headings, bullet points, and bold text for maximum readability and engagement.\n\n**Before generating the full study guide, please confirm your understanding of this refined prompt and ask any clarifying questions about the course content or structure if needed.**\"\n", "category": "Mine", "tags": "prompt", "created_at": "2026-04-07 11:56:22", "last_copied": null, "pinned": 0 }, { "id": 25, "title": "summarize prompts", "content": "## Summary Presets for different summarization styles\n\nVery short summary for quick scanning\nAs a concise summarization expert who distills complex content into its absolute essence.\nCreate an ultra-brief TL;DR summary in 2-3 sentences. Focus only on the most critical takeaway. Be direct and eliminate all fluff.\nPlain text, 2-3 sentences maximum\n\n---\n\nBalanced summary with key points\nAs a professional content analyst who creates clear, balanced summaries.\nProvide a comprehensive yet concise summary that captures the main ideas and important details. Organize into coherent paragraphs. Aim for 5-8 sentences.\nPlain text paragraphs\n\n---\n\nStructured list of key takeaways\nAs an expert at extracting and organizing information into clear, actionable points.\nExtract the main ideas and present them as concise bullet points. Each point should be self-contained and meaningful. Group related points under headings if applicable. Aim for 5-10 key points.\nMarkdown bullet list with optional headings\n\n---\n\nExplain like I am 5 - simple explanations\nAs a patient teacher who explains complex topics in the simplest possible terms using analogies and everyday language.\nSummarize the content as if explaining to someone with no background knowledge. Use simple language, relatable analogies, and avoid jargon. Make it accessible and easy to understand.\nPlain, simple language\n\n---\n\nWell-organized summary with sections\nAs an expert editor and technical writer.\nSummarize the transcript using clear sections. Preserve technical accuracy. Do not invent information.\noutputFormat: 1. Overview\\n2. Key Points\\n3. Examples or Demonstrations\\n4. Final Takeaway", "category": "Dev", "tags": "ai prompt", "created_at": "2026-03-30 07:21:14", "last_copied": null, "pinned": 0 }, { "id": 24, "title": "Docker Stop", "content": "docker-compose down", "category": "Dev", "tags": "docker", "created_at": "2026-01-29 05:36:53", "last_copied": null, "pinned": 0 }, { "id": 23, "title": "Create New Agent Skill", "content": "# Agent Skills - Specs\n\n> The complete format specification for Agent Skills.\n\nThis document defines the Agent Skills format.\n\n## Directory structure\n\nA skill is a directory containing at minimum a `SKILL.md` file:\n\n```\nskill-name/\n└── SKILL.md # Required\n```\n\n\n You can optionally include [additional directories](#optional-directories) such as `scripts/`, `references/`, and `assets/` to support your skill.\n\n\n## SKILL.md format\n\nThe `SKILL.md` file must contain YAML frontmatter followed by Markdown content.\n\n### Frontmatter (required)\n\n```yaml theme={null}\n---\nname: skill-name\ndescription: A description of what this skill does and when to use it.\n---\n```\n\nWith optional fields:\n\n```yaml theme={null}\n---\nname: pdf-processing\ndescription: Extract text and tables from PDF files, fill forms, merge documents.\nlicense: Apache-2.0\nmetadata:\n author: example-org\n version: \"1.0\"\n---\n```\n\n| Field | Required | Constraints |\n| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------- |\n| `name` | Yes | Max 64 characters. Lowercase letters, numbers, and hyphens only. Must not start or end with a hyphen. |\n| `description` | Yes | Max 1024 characters. Non-empty. Describes what the skill does and when to use it. |\n| `license` | No | License name or reference to a bundled license file. |\n| `compatibility` | No | Max 500 characters. Indicates environment requirements (intended product, system packages, network access, etc.). |\n| `metadata` | No | Arbitrary key-value mapping for additional metadata. |\n| `allowed-tools` | No | Space-delimited list of pre-approved tools the skill may use. (Experimental) |\n\n#### `name` field\n\nThe required `name` field:\n\n* Must be 1-64 characters\n* May only contain unicode lowercase alphanumeric characters and hyphens (`a-z` and `-`)\n* Must not start or end with `-`\n* Must not contain consecutive hyphens (`--`)\n* Must match the parent directory name\n\nValid examples:\n\n```yaml theme={null}\nname: pdf-processing\n```\n\n```yaml theme={null}\nname: data-analysis\n```\n\n```yaml theme={null}\nname: code-review\n```\n\nInvalid examples:\n\n```yaml theme={null}\nname: PDF-Processing # uppercase not allowed\n```\n\n```yaml theme={null}\nname: -pdf # cannot start with hyphen\n```\n\n```yaml theme={null}\nname: pdf--processing # consecutive hyphens not allowed\n```\n\n#### `description` field\n\nThe required `description` field:\n\n* Must be 1-1024 characters\n* Should describe both what the skill does and when to use it\n* Should include specific keywords that help agents identify relevant tasks\n\nGood example:\n\n```yaml theme={null}\ndescription: Extracts text and tables from PDF files, fills PDF forms, and merges multiple PDFs. Use when working with PDF documents or when the user mentions PDFs, forms, or document extraction.\n```\n\nPoor example:\n\n```yaml theme={null}\ndescription: Helps with PDFs.\n```\n\n#### `license` field\n\nThe optional `license` field:\n\n* Specifies the license applied to the skill\n* We recommend keeping it short (either the name of a license or the name of a bundled license file)\n\nExample:\n\n```yaml theme={null}\nlicense: Proprietary. LICENSE.txt has complete terms\n```\n\n#### `compatibility` field\n\nThe optional `compatibility` field:\n\n* Must be 1-500 characters if provided\n* Should only be included if your skill has specific environment requirements\n* Can indicate intended product, required system packages, network access needs, etc.\n\nExamples:\n\n```yaml theme={null}\ncompatibility: Designed for Claude Code (or similar products)\n```\n\n```yaml theme={null}\ncompatibility: Requires git, docker, jq, and access to the internet\n```\n\n\n Most skills do not need the `compatibility` field.\n\n\n#### `metadata` field\n\nThe optional `metadata` field:\n\n* A map from string keys to string values\n* Clients can use this to store additional properties not defined by the Agent Skills spec\n* We recommend making your key names reasonably unique to avoid accidental conflicts\n\nExample:\n\n```yaml theme={null}\nmetadata:\n author: example-org\n version: \"1.0\"\n```\n\n#### `allowed-tools` field\n\nThe optional `allowed-tools` field:\n\n* A space-delimited list of tools that are pre-approved to run\n* Experimental. Support for this field may vary between agent implementations\n\nExample:\n\n```yaml theme={null}\nallowed-tools: Bash(git:*) Bash(jq:*) Read\n```\n\n### Body content\n\nThe Markdown body after the frontmatter contains the skill instructions. There are no format restrictions. Write whatever helps agents perform the task effectively.\n\nRecommended sections:\n\n* Step-by-step instructions\n* Examples of inputs and outputs\n* Common edge cases\n\nNote that the agent will load this entire file once it's decided to activate a skill. Consider splitting longer `SKILL.md` content into referenced files.\n\n## Optional directories\n\n### scripts/\n\nContains executable code that agents can run. Scripts should:\n\n* Be self-contained or clearly document dependencies\n* Include helpful error messages\n* Handle edge cases gracefully\n\nSupported languages depend on the agent implementation. Common options include Python, Bash, and JavaScript.\n\n### references/\n\nContains additional documentation that agents can read when needed:\n\n* `REFERENCE.md` - Detailed technical reference\n* `FORMS.md` - Form templates or structured data formats\n* Domain-specific files (`finance.md`, `legal.md`, etc.)\n\nKeep individual [reference files](#file-references) focused. Agents load these on demand, so smaller files mean less use of context.\n\n### assets/\n\nContains static resources:\n\n* Templates (document templates, configuration templates)\n* Images (diagrams, examples)\n* Data files (lookup tables, schemas)\n\n## Progressive disclosure\n\nSkills should be structured for efficient use of context:\n\n1. **Metadata** (\\~100 tokens): The `name` and `description` fields are loaded at startup for all skills\n2. **Instructions** (\\< 5000 tokens recommended): The full `SKILL.md` body is loaded when the skill is activated\n3. **Resources** (as needed): Files (e.g. those in `scripts/`, `references/`, or `assets/`) are loaded only when required\n\nKeep your main `SKILL.md` under 500 lines. Move detailed reference material to separate files.\n\n## File references\n\nWhen referencing other files in your skill, use relative paths from the skill root:\n\n```markdown theme={null}\nSee [the reference guide](references/REFERENCE.md) for details.\n\nRun the extraction script:\nscripts/extract.py\n```\n\nKeep file references one level deep from `SKILL.md`. Avoid deeply nested reference chains.\n\n## Validation\n\nUse the [skills-ref](https://github.com/agentskills/agentskills/tree/main/skills-ref) reference library to validate your skills:\n\n```bash theme={null}\nskills-ref validate ./my-skill\n```\n\nThis checks that your `SKILL.md` frontmatter is valid and follows all naming conventions.\n\n\n---\n\n\nAbove is the skill creation guide\nI want you to create a skill to make file for my apps docker deployment on my vps, later you will use it for this particular web app \nI use nginx.conf, and caddy for network (I have one master called: caddy_network).\nI like to use explicit client/frontend_ +\"example_app\" for docker image name.\n\nhere is an example of a prompt I have used in the past:\n# Prompt to deploy\n\nI need to containerize this application with docker for my vps using lightweight images.\nI already have a container for networks \"caddy_network\" so my Caddy server can route traffic to it (from `www.agebond.haguma.com`).\n\nCreate a multi-stage `Dockerfile` for the React frontend.\nThe final stage should use a lightweight Nginx image to serve the production build.\nThe Nginx configuration (`nginx.conf`) should serve the React app and also act as a reverse proxy, forwarding any requests to `/api/...` to the `backend` service.\nUpdate the frontend code so that API calls are made to a relative path\n\nAlso I will need to initialize and make migrations (in of database)", "category": "Dev", "tags": "txt", "created_at": "2026-01-25 12:27:55", "last_copied": null, "pinned": 0 }, { "id": 22, "title": "Emails and stuff", "content": "dropbox\n-------\nmyfabg@yahoo.fr ([vizzdaku]) \n\n\ngoogle1\n-------\nfabruz3@gmail.com ([vizzdaku123]) \n\n\ngoogle2\n-------\nhagumfab@gmail.com ([vizzkadu123]) \n\n \ngoogle3\n-------\njonifab3@gmail.com (*inezafab*)fabjoni \n\n\nyahoo1\n------\nmyfabg@yahoo.fr ([vizzkadu123]) \n\n\nyahoo2\n------\nhagumaf@yahoo.com ([gisele])\n\n\nyahoo3\n------\nsinzineti@ymail.com ([vizzkadu])\nsinzineti(fb) ([vizzkadu]) \n \n\nlinkedin \n--------\nmyfabg@yahoo.fr ([vizzkadu123])\n", "category": "Moi", "tags": "txt", "created_at": "2026-01-25 06:53:28", "last_copied": null, "pinned": 0 }, { "id": 21, "title": "Solution Engineer - buckhill-remote croatia", "content": "Worldwide, Croatia · Employee/Contractor · Remote\nJob description\nBuckhill is a global technology company with offices in the UK and Croatia. As a strategic technology partner to the London Market, we deliver modern insurance solutions through agile, cross-functional delivery teams leveraging AI capabilities, a growing partner ecosystem, and a culture rooted in innovation and collaboration. We support continuous learning and invest in the growth of our Bucks, fostering an environment where people thrive. With the option for remote work, we've expanded our global footprint, building a diverse and multicultural team making a real impact. \n\nWe're looking for a Solutions Engineer to convert client business challenges into functional solutions and designs. You'll handle client inquiries, problems, and incidents within your portfolio while working with our development and delivery teams to implement solutions. This role requires pattern recognition, systematic thinking, and the ability to identify improvements in systems, processes, and products. You must communicate effectively with both technical and non-technical audiences. \n\nSalary Ranges\n\n Croatia: €2.2k - €2.7k (Gross 1, monthly)\n\n Croatia: €26.4k - €32.4k (Gross 1, annual)\n\n United Kingdom: £34k - £41k (Gross, annual)\n\n Europe, outside of Croatia: €27k - €41k (Gross 2, annual)\n\n Africa & Sri Lanka: €27k - €37k (Gross 2, annual)\n\n Rest of the world: €27k - €56k (Gross 2, annual)\n\nJob requirements\n\n Degree or equivalent practical experience \n\n At least 3 years of relevant work experience \n\n Demonstrated ability to work independently with moderate direction \n\n Advanced English (written and conversational) \n\nTechnical knowledge of: \n\n Technical documentation and specification writing \n\n Basic JS ES5 knowledge \n\n Service Oriented Architecture fundamentals \n\n PaaS platforms \n\n SQL, HTML and CSS \n\n Configuration languages (XML, JSON, YAML) \n\n Modeling techniques (ERD, UML, ad-hoc diagramming) \n\n Software Development Lifecycle, including CI/CD \n\n REST API design and GraphQL basics \n\n Distributed architectures and microservices concepts \n\n Security architecture principles \n\n Enterprise architecture concepts (IAM, MDM) \n\n Enterprise Integration Patterns and EAI frameworks \n\nJob responsibilities\n\n Design software tools and systems specifications for delivery teams to implement \n\n Build proof of concept systems in low-code environments \n\n Translate client requirements into detailed project plans and technical specifications for the Development department\n\n Support the definition of systems and architectural standards (under guidance from senior team members) \n\n Resolve technical incidents, problems, and queries requiring solution design \n\n Escalate complex issues appropriately while taking ownership of mid-complexity problems ", "category": "Jobpost", "tags": "txt", "created_at": "2026-01-25 04:04:52", "last_copied": null, "pinned": 0 }, { "id": 20, "title": "Senior Backend Engineer - Hostaway", "content": "Senior Backend Engineer, AI Integrations - 100% Remote - EMEA\nRemote\nVienna, Wien, Austria•\n+17 more\nEngineering\nJob details\nApply\nJob description\nNOTE: This is a FULLY remote role, but the candidate must be within EMEA to collaborate with their team, peers, and internal customers. You do not have to be in the specific country or city shown in this listing, but please only apply if you are physically based within EMEA.\n\nHostaway is a SaaS scale-up that is transforming the vacation rental industry. With innovative solutions and partnerships with giants like Airbnb, VRBO, and Booking, we're taking on the competition and winning. Leveraging our customer-centric core values, we consistently deliver results that encourage growth, learning, and innovation for our team, our customers, and the industry.\n\n\nProfitable, high-growth, and the first short-term rental Property Management System unicorn 🦄. Join us at our most exciting stage yet! Learn more about our recent valuation and story here.\n\nAbout the role\nAs a Senior Backend Engineer on our AI Team, you’ll focus on integrating AI services into Hostaway’s product. You’ll turn raw data and models into polished, customer-facing features by working in Python, building APIs, services, and UIs that make AI useful for property managers and guests.\n\nYou’ll work closely with product and platform teams to ensure AI components slot seamlessly into our SaaS ecosystem - from automation workflows to customer insights dashboards.\n\nWhat you’ll do:\nDesign and build services that integrate AI into customer-facing features.\n\nDevelop performant and scalable APIs and backend services that connect AI outputs to SaaS functionality.\n\nCollaborate with product and design teams to create intuitive AI-driven user experiences.\n\nPartner with platform and integration teams to embed AI into existing systems and workflows.\n\nImplement observability, monitoring, and error handling for AI services in production.\n\nContribute to evolving our AI integration stack (TypeScript SDKs, MCP servers, LLM orchestration).\n\nJob requirements\n5+ years in backend engineering, ideally SaaS.\n\nStrong Python or PHP proficiency, ideally both.\n\nExperience with REST APIs and SaaS integrations.\n\nFamiliarity with LLM/AI tools in the JS or Python ecosystem (LangChain, Vercel AI SDK, MCP servers).\n\nComfortable working alongside Python-based AI services and bridging stacks.\n\nBonus: experience with Golang\n\nStrong collaboration skills - able to integrate work with platform and product teams.\n\nWhat success looks like:\nAI-powered features are seamlessly embedded into Hostaway’s SaaS product.\n\nCustomer workflows feel smarter, faster, and more personalized thanks to your integrations.\n\nAI services are stable, observable, and easy to maintain.\n\nYou become a go-to engineer for AI product integration across Hostaway.\n\nWhat we offer\nCompetitive Compensation: We offer competitive pay based on market rates in the country of the applicant.\n\n100% Remote: Enjoy the freedom to work from anywhere within your country of residence—be it a co-working space, your home office, or even your dining room table. The choice is yours. Just don’t ask to work in our office (we don’t have one).\n\nEquity: Every role in our company comes with valuable stock options in a fast-growing and profitable company. This ensures we all share in the company’s success.\n\nValues-Driven Leadership: Our Core Values are not just words we’ve written to make us feel good. We leverage them daily when making strategic and tactical decisions.\n\nProfessional Growth: Our rapid growth offers unparalleled learning and development opportunities, along with a multitude of career advancement opportunities.\n\nAnnual Paid Leave: The specific amounts vary by country and are aligned with country and/or contract-specific norms.\n\nGeographic Specific Benefits: As an international employer, we offer different country-specific benefits such as Health Insurance and Pensions in countries where these perks are customary. The specifics depend on the country of the applicant.\n\nDynamic Team Culture: As a global company with team members in over 40 countries, our diverse and international culture fuels our innovation and creativity, providing a key pillar to our success (and making it a lot of fun to work here).\n\nThank you for your interest. If you apply for this role, you will receive an email from our Talent Acquisition team after your application has been reviewed alongside the qualifications for this role and the qualifications of others who have applied.\n", "category": "Jobpost", "tags": "txt", "created_at": "2026-01-23 06:27:55", "last_copied": null, "pinned": 0 }, { "id": 19, "title": "Backend developer - odiin", "content": "Odiin. logo\nOdiin.\nShare\nShow more options\nBack End Developer \nEMEA · Reposted 18 hours ago · Over 100 applicants\nPromoted by hirer · Actively reviewing applicants\n\n\n Remote\nMatches your job preferences, workplace type is Remote.\n\n Contract\nMatches your job preferences, job type is Contract.\nApplied 1 minute ago\nSee applicationApplied 1 minute ago for Back End Developer\nBack End Developer\nOdiin. · EMEA (Remote)\nApplied 1 minute ago\nShow more options\nTake the next step in your job search\nGet AI-powered advice on this job and more exclusive features with Premium. Try Premium for $0\n\n\n\nPractice an interview\n\nAbout the job\nYou will be responsible for designing, building, and maintaining the server-side logic, databases, and APIs that power our applications. Your role will involve optimizing performance, ensuring scalability, and collaborating with front-end developers and other stakeholders to deliver seamless user experiences.\n\n\nKey Responsibilities:\n\nDevelop, test, and maintain scalable backend applications and APIs.\nDesign and optimize database structures for performance and reliability.\nImplement security best practices to protect sensitive data.\nCollaborate with front-end developers to integrate user-facing elements with server-side logic.\n\n\nRequirements:\n\nStrong proficiency in backend programming languages (e.g., Python, Node.js, Java, Go, Ruby, or C#).\nExperience with frameworks like Django, Express.js, Spring Boot, or similar.\nProficiency in working with relational and/or NoSQL databases (e.g., PostgreSQL, MySQL, MongoDB).\nExperience building and consuming RESTful and/or GraphQL APIs.\nFamiliarity with cloud platforms (AWS, GCP, Azure) and containerization (Docker, Kubernetes).\n\n\nPreferred Qualifications:\n\nExperience with microservices architecture.\nKnowledge of caching strategies (Redis, Memcached).\nBackground in message queues (Kafka, RabbitMQ).\nPrevious experience working in a fast-paced startup or tech-driven company.", "category": "Jobpost", "tags": "txt", "created_at": "2026-01-23 06:17:43", "last_copied": null, "pinned": 0 }, { "id": 18, "title": "Christine Tiktok", "content": "\nProfile name: chris\nUsername: u.christine", "category": "Moi", "tags": "", "created_at": "2026-01-19 13:16:24", "last_copied": null, "pinned": 0 }, { "id": 17, "title": "VPS SSH", "content": "ssh -i C:\\Users\\Fabrice\\.ssh\\my_vps_key fabrice@141.11.167.158", "category": "Dev", "tags": "vps ssh", "created_at": "2026-01-17 05:54:08", "last_copied": null, "pinned": 0 }, { "id": 16, "title": "M365Consult - Python Backend Dev", "content": "{\n \"job_title\": \"Python Selenium Django Backend Developer\",\n \"company_name\": \"M365Consult\",\n \"company_description\": \"M365Consult is a dynamic European consulting firm specializing in Microsoft solutions and innovative software projects. We seek skilled Python developers passionate about backend development using Django, Selenium, and API/database architecture for impactful, scalable applications.\",\n \"contract_type\": \"Full-time\",\n \"seniority_level\": null,\n \"department\": null,\n \"location\": \"DACH Region\",\n \"is_remote\": true,\n \"job_description\": \"Develop, maintain, and enhance backend architecture for web applications with a focus on Django stack, RESTful APIs, and database design. Collaborate closely with front-end teams to ensure seamless user experience integration. Implement Python scripting for automation and efficient data management.\\n\\nWhat We Offer:\\nEngaging projects with direct impact on digital recruitment.\\nFlexible remote working hours and supportive work environment.\\nOpportunities for professional growth in Microsoft and open-source tech.\",\n \"responsibilities\": [\n \"Develop backend functionality with Django framework and Python.\",\n \"Build and maintain APIs and database architecture.\",\n \"Use Selenium and web scraping tools like Bs4 and requests for data extraction.\",\n \"Handle complex web crawling and Google search integrations for company website and email extraction.\",\n \"Manage data deduplication and merging across sources.\",\n \"Produce well-documented code, diagrams, and testing suites.\",\n \"Support the integration of front-end components (HTML, CSS).\",\n \"Work on multiple job scraping platforms including LinkedIn, Glassdoor, and Indeed.\"\n ],\n \"requirements\": \"Skilled Python developers passionate about backend development using Django, Selenium, and API/database architecture. Proficiency in Python, Django framework, RESTful APIs, and database design is essential. Experience with web scraping tools (Selenium, Bs4, requests), complex web crawling, and Google search integrations for data extraction (job titles, locations, company names, descriptions, URLs, company websites, email addresses). Ability to manage data deduplication and merging across various sources (e.g., LinkedIn, Glassdoor, Indeed). Knowledge of front-end components (HTML, CSS) for integration and dashboard development. Strong focus on producing well-documented code, diagrams, and testing suites.\",\n \"skills\": null,\n \"experience\": null,\n \"education\": null,\n \"application_deadline\": null\n}", "category": "Jobpost", "tags": "json", "created_at": "2026-01-15 10:54:31", "last_copied": null, "pinned": 0 }, { "id": 15, "title": "Scanz-Remote Full-Stack Developer", "content": "{\n \"job_title\": \"Remote Full-Stack Developer (Kotlin/Java/React + AI Focus)\",\n \"company_name\": \"Scanz\",\n \"company_description\": \"Scanz has been working for nearly two decades in the real-time trading technology and fintech space. We operate a market-leading SaaS platform that delivers complex technological systems for serious traders worldwide. Scanz is the fastest and most actionable trading platform ever created for monitoring live, market-moving activity. Our proprietary terminal brings together powerful scanners, alerts, newsfeeds, charts, unique montages and customizable layouts within a beautifully designed and intuitive platform.\",\n \"contract_type\": \"Full Time / Perm\",\n \"seniority_level\": null,\n \"department\": null,\n \"location\": \"Europe\",\n \"is_remote\": true,\n \"job_description\": \"We are seeking a versatile Full-Stack Developer with strong backend foundations to join our team and contribute across multiple areas of our platform, from server-side systems to billing infrastructure to desktop applications. This role is ideal for someone who thrives working across the stack and is passionate about leveraging AI tools and LLMs to accelerate development and build intelligent features.\\n\\nYou will primarily work with Kotlin/Java on the backend and TypeScript on the frontend, with significant exposure to our Electron desktop application and billing/accounts systems. A key aspect of this role involves pioneering our AI-first development practices, which consists of building AI-powered features for our users and establishing internal AI tooling and workflows.\",\n \"responsibilities\": [\n \"Design and implement server-side logic using Spring Webflux and Kotlin.\",\n \"Build robust, reliable, fault-tolerant data pipelines that process millions of operations daily.\",\n \"Collaborate with front-end developers to integrate user-facing elements with server-side logic.\",\n \"Maintain and enhance our user accounts backend APIs\",\n \"Contribute to our Electron desktop application and common client libraries\",\n \"Develop and maintain APIs, ensuring high performance and responsiveness\",\n \"Contribute to database design and implementation (PostgreSQL)\",\n \"Participate in code reviews and daily remote standups\",\n \"Champion AI-first development practices across the team\",\n \"Build and maintain AI-powered features for our trading platform\",\n \"Develop internal AI tooling: agents for documentation, architecture analysis, code assistance, and workflow automation\",\n \"Experiment with and evaluate emerging LLM capabilities and integrate them into our development processes\",\n \"Create and optimize prompts, context systems, and AI workflows\",\n \"Help onboard team members to AI-assisted development practices\"\n ],\n \"requirements\": \"Technical Skills:\\n- Strong proficiency in Kotlin and Java\\n- Proficiency with TypeScript and modern frontend frameworks (React, Vue.js)\\n- Experience with Electron or desktop application development (preferred)\\n- Familiarity with Spring Webflux, reactive programming concepts\\n- Experience with billing/payments systems (Stripe, subscription management) is a plus\\n- Comfortable with database systems, particularly PostgreSQL\\n- Experience with containerization technologies (Docker, Kubernetes)\\n- Comfortable using AWS and cloud computing platforms\\n- Solid understanding of testing practices (unit, integration, E2E)\\n\\nAI & LLM Experience:\\n- Demonstrated experience using advanced AI development workflows\\n- Experience with LLM APIs and prompt engineering\\n- Experience building AI-powered features or agents\\n- Enthusiasm for exploring and pushing the boundaries of AI-assisted development\\n- Model fine tuning (nice to have)\\n- RAG implementation (nice to have)\\n\\nSoft Skills:\\n- Self-motivated and comfortable working across multiple domains\\n- Strong problem-solving skills and ability to context-switch effectively\\n- Excellent collaboration and communication skills within an asynchronous environment (Slack, Loom)\\n- Willingness to learn new technologies and adapt quickly\\n- Curious mindset with eagerness to experiment with emerging tools and approaches\",\n \"skills\": \"Backend: Kotlin, Java, Spring Webflux, Kotlin Coroutines, RSocket, PostgreSQL, Mongodb, JUnit, TestContainers, Gradle, Express JS\\nFrontend & Desktop: TypeScript, React, Vue.js, Electron, Kotlin Multiplatform, NPM\\nInfrastructure: AWS, S3, Prometheus, Grafana, Jenkins, GitHub, Docker, Kubernetes\\nAI/LLM: Claude API, OpenRouter, Braintrust, AI coding assistants, Vercel AI SDK\",\n \"experience\": \"Demonstrated experience using advanced AI development workflows. Experience with building AI-powered features or agents.\",\n \"education\": null,\n \"application_deadline\": null\n}", "category": "Jobpost", "tags": "json", "created_at": "2026-01-15 08:50:38", "last_copied": null, "pinned": 0 }, { "id": 13, "title": "Frontend Design Skills", "content": "---\nname: frontend-design\ndescription: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.\nlicense: Complete terms in LICENSE.txt\n---\n\nThis skill guides creation of distinctive, production-grade frontend interfaces that avoid generic \"AI slop\" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.\n\nThe user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.\n\n## Design Thinking\n\nBefore coding, understand the context and commit to a BOLD aesthetic direction:\n- **Purpose**: What problem does this interface solve? Who uses it?\n- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.\n- **Constraints**: Technical requirements (framework, performance, accessibility).\n- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?\n\n**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.\n\nThen implement working code (HTML/CSS/JS, React, Vue, etc.) that is:\n- Production-grade and functional\n- Visually striking and memorable\n- Cohesive with a clear aesthetic point-of-view\n- Meticulously refined in every detail\n\n## Frontend Aesthetics Guidelines\n\nFocus on:\n- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.\n- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.\n- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.\n- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.\n- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.\n\nNEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.\n\nInterpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.\n\n**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.\n\nRemember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.\n", "category": "Dev", "tags": "ai", "created_at": "2026-01-14 07:44:29", "last_copied": null, "pinned": 0 }, { "id": 12, "title": "Job Post JSON", "content": "{\n \"job_title\": null,\n \"company_name\": null,\n \"company_description\": null,\n \"contract_type\": null,\n \"seniority_level\": null,\n \"department\": null,\n \"location\": null,\n \"is_remote\": null,\n \"job_description\": null,\n \"responsibilities\": [],\n \"requirements\": null,\n \"skills\": null,\n \"experience\": null,\n \"education\": null,\n \"application_deadline\": null\n}", "category": "Mine", "tags": "json", "created_at": "2026-01-14 07:43:09", "last_copied": null, "pinned": 0 }, { "id": 11, "title": "Java Spring Boot Run", "content": "./mvnw spring-boot:run", "category": "Dev", "tags": "java run start", "created_at": "2026-01-14 07:41:36", "last_copied": null, "pinned": 0 }, { "id": 10, "title": "My Linkedin", "content": "https://www.linkedin.com/in/fabrice-haguma/", "category": "Moi", "tags": "linkedin", "created_at": "2026-01-14 07:38:00", "last_copied": null, "pinned": 0 }, { "id": 9, "title": "My Github", "content": "https://github.com/fabhaguma", "category": "Moi", "tags": "github", "created_at": "2026-01-14 07:37:32", "last_copied": null, "pinned": 0 }, { "id": 8, "title": "My Portfolio", "content": "https://www.portfolio.haguma.com/", "category": "Moi", "tags": "portfolio", "created_at": "2026-01-14 07:36:58", "last_copied": null, "pinned": 0 }, { "id": 7, "title": "My Email", "content": "fabruz3@gmail.com", "category": "Moi", "tags": "email", "created_at": "2026-01-14 07:35:53", "last_copied": null, "pinned": 0 }, { "id": 6, "title": "Docker Logs", "content": "docker-compose logs -f backend_xxxx", "category": "Dev", "tags": "docker", "created_at": "2026-01-14 07:33:29", "last_copied": null, "pinned": 0 }, { "id": 5, "title": "Docker Up", "content": "docker-compose up -d --build", "category": "Dev", "tags": "docker", "created_at": "2026-01-14 07:31:56", "last_copied": null, "pinned": 0 } ]