Misc Learnings

https://www.udemy.com/course/basic-to-advanced-retreival-augmented-generation-rag-course/ Role of RAG in Enhancing LLM Capabilities Improve factual consistency Enhance domain specific knowledge Reduce Hallucination Install Ollama and run to exit type "/bye" Github Repo :  https://github.com/whyashthakker/RAG   Vectors  https://xomnia.com/post/an-introduction-to-vector-databases-for-beginners/ Different Embedding Models https://medium.com/@kashyapkathrani/all-about-embeddings-829c8ff0bf5b Vector Databases Store and Search Vector Embeddings Can also index data Scale data

 In the strict OAuth 2.0 specification, claims are not a required component of an access token. However, in modern practice—especially when using OpenID Connect (OIDC) —claims are frequently included if the token is formatted as a JWT (JSON Web Token) . The presence of claims depends entirely on the token format chosen by the Authorization Server: 1. JWT Access Tokens (The Modern Standard) Most modern identity providers (like Okta, Auth0, or AWS Cognito) issue access tokens as JWTs. In this scenario, yes, claims are part of the access token . Standard Claims: You will find claims like sub (subject/user ID), iss (issuer), exp (expiration), and iat (issued at). Authorization Claims: The scope claim is usually included to tell the Resource Server what the bearer is allowed to do. Custom Claims: Organizations often inject custom claims (e.g., tenant_id , org_unit , or user_role ) to allow microservices to make authorization decisions without hitting a database. 2. Opaque Acce...

 The core difference is that OAuth 2.0 is an authorization framework, while OpenID Connect (OIDC) is an authentication layer built on top of it. Think of OAuth 2.0 as a key card that grants you access to specific rooms in a hotel (the resources), and OIDC as the ID badge that actually identifies who you are. 1. Primary Purpose OAuth 2.0: Designed to provide Delegated Access . It allows a third-party application to access a user's data (like photos or contacts) without needing the user's password. It answers the question: "What is this application allowed to do?" OIDC: Designed for Identity . It sits on top of OAuth 2.0 to provide information about the user. It answers the question: "Who is the user, and how did they log in?" 2. The Token Types The most visible difference in the protocol flow is the type of tokens issued: OAuth 2.0 issues an Access Token: This is usually an "opaque" string or a JWT intended for the Resource Server . It does...

https://www.youtube.com/watch?v=BDxRhhs36ns&list=PL0lo9MOBetEHvO-spzKBAITkkTqv4RvNl Then Login

https://www.youtube.com/watch?v=LorEJPrALcg To add multiple repositories using the BMAD Federated Knowledge System (bmad-fed), you can use the bmad-fed add command in either an interactive or command-line mode. 1. Interactive Mode : This is the simplest way to add repositories one by one, as the system will prompt you for all required details.bashbmad-fed add <repo-name> --interactive Use code with caution.During the prompts, select "Repository" as the knowledge type. 2. Command-Line Mode : For more precise control, you can specify all parameters directly. To add multiple repositories, run the command separately for each one:bash# Adding the first repository bmad-fed add repo1 \ --repo git@github.com:user/repo1.git \ --branch main \ --priority 1 \ --sync-policy daily # Adding a second repository bmad-fed add repo2 \ --repo git@github.com:user/repo2.git \ --branch main \ --priority 2 \ --sync-policy daily  

https://www.youtube.com/watch?v=goOZSXmrYQ4 https://github.com/coleam00/link-in-bio-page-builder/blob/main/AICodingWithLargeCodebases.png Don't recommend using subagents for implementing , coz you need whole context https://github.com/coleam00/link-in-bio-page-builder/blob/main/.claude/commands/create-prd.md after chatting create PRD after PRD make modular rules